CVE-2026-98457: Linux kernel · Bluetooth: L2CAP: validate frame length before control and FCS access
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f557274af7b94b6134692e6f26b880f1e34c15bf : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f557274af7b94b6134692e6f26b880f1e34c15bf, c6a288e6001bcce16553c3853e0f5a45eaaf85c7, 4373ba79a267947e771c438507f7b103e30bdb21 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in specific Linux kernel commits. Users and administrators should update affected Linux kernel versions to the fixed releases identified by the provided commit hashes to remediate this issue.
Description
A vulnerability in the Linux kernel's Bluetooth L2CAP implementation allows out-of-bounds reads due to improper validation of frame length before accessing control and FCS fields. This flaw affects version 2.6.32 and is fixed in later commits. The issue arises when short frames are processed without verifying their length, potentially leading to memory access beyond the buffer.
References
- git.kernel.org/stable/c/4373ba79a267947e771c438507f7b103e30bdb21 (opens in a new tab)
- git.kernel.org/stable/c/965bd88ed4b4763cb765dd65885adcfa588c6b14 (opens in a new tab)
- git.kernel.org/stable/c/3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70 (opens in a new tab)
- git.kernel.org/stable/c/8c7556c7cd17e073bbefdc4a9a4694a207544c37 (opens in a new tab)
- git.kernel.org/stable/c/1fdbb2a712a9a162ee817c959740face80b3d929 (opens in a new tab)
- git.kernel.org/stable/c/c6a288e6001bcce16553c3853e0f5a45eaaf85c7 (opens in a new tab)
- git.kernel.org/stable/c/f557274af7b94b6134692e6f26b880f1e34c15bf (opens in a new tab)
- git.kernel.org/stable/c/6c78a213d9070b610c7f418af2c25b66180b7e37 (opens in a new tab)