CVE-2026-64403
Description
A flaw was found in the Bluetooth L2CAP (Logical Link Control and Adaptation Protocol) component of the Linux kernel. The l2cap_get_conf_opt() function, responsible for processing configuration options, does not properly validate the length of an option before attempting to read its value. This allows an attacker to control the option length, potentially leading to an out-of-bounds read of up to 4 bytes past the end of a buffer. Although current safeguards prevent immediate data leakage, this vulnerability represents a critical validate-after-use ordering bug that could be exploited in future system configurations.
Statement
A validate after use bug in Bluetooth L2CAP configuration parsing allows l2cap_get_conf_opt() to read opt val before confirming that the full attacker controlled option length is present in the buffer. A nearby remote Bluetooth peer can send a malformed L2CAP configuration option and trigger an out of bounds read of up to 4 bytes before the caller detects the malformed length. For the CVSS the PR:N is used because triggering does not require local privileges on the victim and only requires the ability to interact with the Bluetooth L2CAP path. The issue is adjacent network reachable rather than Internet reachable because Bluetooth proximity or link access is normally required. Impact is primarily denial of service or a hardened kernel warning. The worst case is limited confidentiality impact and high availability impact, not privilege escalation, because the patch shows an out of bounds read but not a write primitive or UAF.
Mitigation
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.5 | N/A | 7.1 |
| Attack Vector | Adjacent Network | N/A | Adjacent Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory)
An attacker could provide unexpected values and cause a program crash or arbitrary control of resource allocation, leading to excessive consumption of resources such as memory and CPU.
Confidentiality
Technical Impact: Read Memory; Read Files or Directories
An attacker could read confidential data if they are able to control resource references.
Integrity,Confidentiality,Availability
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
An attacker could use malicious input to modify data or possibly alter control flow in unexpected ways, including arbitrary command execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.