LiveActive security incident?Get immediate response
CVE Record

CVE-2020-25661: A Red Hat only CVE-2020-12351 regression issue was found in the way the Linux kernel's Bluetooth implementa...

A Red Hat only CVE-2020-12351 regression issue was found in the way the Linux kernel's Bluetooth implementation handled L2CAP packets with A2MP CID. This flaw allows a remote attacker in an adjacent range to crash the system, causing a denial of service or potentially executing arbitrary code on the system by sending a specially crafted L2CAP packet. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-25661 is a Red Hat-specific Linux kernel Bluetooth flaw affecting kernel-4.18.0-240.el8. A nearby attacker could send malicious Bluetooth L2CAP traffic and crash the system, with potential arbitrary code execution according to the CVE description. This is not an internet-facing issue, but it matters for laptops, kiosks, workstations, and servers with Bluetooth enabled.

Executive priority

Treat as high priority for affected Red Hat endpoints with Bluetooth enabled, especially mobile or public-facing physical environments. The practical exposure is narrower than internet-facing vulnerabilities, but the potential confidentiality, integrity, and availability impact justifies prompt inventory and vendor-guided remediation.

Technical view

The issue is described as a Red Hat-only regression related to CVE-2020-12351 in Linux kernel Bluetooth L2CAP handling for A2MP CID packets. It is classified as CWE-843 and scored CVSS 3.1 7.5 with adjacent-network attack vector, high complexity, no privileges, and no user interaction.

Likely exposure

Exposure appears limited to Red Hat systems running kernel-4.18.0-240.el8 where Bluetooth is present and reachable by an attacker in adjacent range. Systems without Bluetooth hardware, with Bluetooth disabled, or not using the affected Red Hat kernel are less likely to be exposed based on the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The described attack requires adjacent-range access, high attack complexity, no credentials, and no user interaction. Impact may include denial of service and potentially arbitrary code execution.

Researcher notes

Evidence is incomplete for exact fixed package versions in the provided bundle. Analysis should stay tied to Red Hat kernel-4.18.0-240.el8 and the Bluetooth L2CAP A2MP CID handling regression. Do not broaden scope to all Linux kernels without additional vendor evidence.

Mitigation direction

  • Inventory Red Hat systems for kernel-4.18.0-240.el8.
  • Check Red Hat CVE and BleedingTooth guidance for supported remediation.
  • Prioritize systems with enabled Bluetooth in public or shared spaces.
  • Evaluate Bluetooth exposure reduction where operationally acceptable and vendor-supported.
  • Track remediation through normal kernel update and reboot governance.

Validation and detection

  • Confirm installed kernel versions on Red Hat hosts.
  • Identify hosts with Bluetooth hardware and enabled Bluetooth services.
  • Review Red Hat advisory status for CVE-2020-25661 guidance.
  • Verify remediated systems no longer run kernel-4.18.0-240.el8.
  • Document exceptions for systems requiring Bluetooth operation.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-843: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-25661 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.65.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-25661Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red Hatkernelkernel-4.18.0-240.el8Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-843 · source CWE mapping

Access of Resource Using Incompatible Type ('Type Confusion')

Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.