CVE-2026-98457: Bluetooth: L2CAP: validate frame length before control and FCS access
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 1fdbb2a712a9a162ee817c959740face80b3d929, 3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70, 4373ba79a267947e771c438507f7b103e30bdb21; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1fdbb2a712a9a162ee817c959740face80b3d929, 3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70, 4373ba79a267947e771c438507f7b103e30bdb21; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: validate frame length before control and FCS access l2cap_data_rcv() unpacks either a two-byte or four-byte control field without first ensuring that it is present. A short ERTM or streaming-mode frame can therefore cause an out-of-bounds read. There is a second short-frame case when CRC16 is enabled. After the control field is pulled, l2cap_check_fcs() subtracts two from skb->len without checking it. If fewer than two bytes remain, the subtraction wraps; skb_trim() leaves the buffer unchanged and the subsequent FCS load reads past the logical end of the frame. Validate that the frame contains both its control field and, when enabled, its FCS before either field is accessed.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.32affected
- 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a and later · before 4373ba79a267947e771c438507f7b103e30bdb21affected · git
- 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a and later · before 965bd88ed4b4763cb765dd65885adcfa588c6b14affected · git
- 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a and later · before 3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70affected · git
- 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a and later · before 8c7556c7cd17e073bbefdc4a9a4694a207544c37affected · git
- 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a and later · before 1fdbb2a712a9a162ee817c959740face80b3d929affected · git
- 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a and later · before c6a288e6001bcce16553c3853e0f5a45eaaf85c7affected · git
- 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a and later · before f557274af7b94b6134692e6f26b880f1e34c15bfaffected · git
- 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a and later · before 6c78a213d9070b610c7f418af2c25b66180b7e37affected · git
- before 2.6.32not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98455Oct 18, 2026 · Bluetooth: RFCOMM: fix NULL dereference of dlc->session in RFCOMM_CONNINFO0Monitor
- ← EarlierCVE-2026-98456Oct 18, 2026 · Bluetooth: mgmt: fix race in read_unconf_index_list()28Monitor
- Later →CVE-2026-98458Oct 18, 2026 · Bluetooth: ISO: release unused CIS holds after channel attach0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1fdbb2a712a9a162ee817c959740face80b3d929 | Vendor (CNA) |
| Linux Linux | 3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70 | Vendor (CNA) |
| Linux Linux | 4373ba79a267947e771c438507f7b103e30bdb21 | Vendor (CNA) |
| Linux Linux | 6c78a213d9070b610c7f418af2c25b66180b7e37 | Vendor (CNA) |
| Linux Linux | 8c7556c7cd17e073bbefdc4a9a4694a207544c37 | Vendor (CNA) |
| Linux Linux | 965bd88ed4b4763cb765dd65885adcfa588c6b14 | Vendor (CNA) |
| Linux Linux | c6a288e6001bcce16553c3853e0f5a45eaaf85c7 | Vendor (CNA) |
| Linux Linux | f557274af7b94b6134692e6f26b880f1e34c15bf | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 9, 2026+22 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3acf6a0038ec0d4e8f4dcbfc2a557dff5f61cb70
- git.kernel.org/stable/c/4373ba79a267947e771c438507f7b103e30bdb21
- git.kernel.org/stable/c/6c78a213d9070b610c7f418af2c25b66180b7e37
- git.kernel.org/stable/c/8c7556c7cd17e073bbefdc4a9a4694a207544c37
- git.kernel.org/stable/c/965bd88ed4b4763cb765dd65885adcfa588c6b14
- git.kernel.org/stable/c/c6a288e6001bcce16553c3853e0f5a45eaaf85c7
- git.kernel.org/stable/c/f557274af7b94b6134692e6f26b880f1e34c15bf
Vendor advisories and official records. Exploit/PoC links are deliberately left out.