CVE-2026-98461: Bluetooth: hci_sock: validate event length before filtering
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 1a92763c2ba721bf113cd83f913fe8c511b4a4dc, 2501a3b7b7144d1d11939b355a48ed01f83d0c62, 3976bbcd43b9b94c53ac9b0fd28888011588f4cc; 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 1a92763c2ba721bf113cd83f913fe8c511b4a4dc, 2501a3b7b7144d1d11939b355a48ed01f83d0c62, 3976bbcd43b9b94c53ac9b0fd28888011588f4cc; 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: hci_sock: validate event length before filtering is_filtered_packet() reads the event code from skb->data[0] without first checking that the skb is nonempty. When an opcode filter is configured, it also reads the command opcode at offsets 3 or 4 without checking that a Command Complete or Command Status event is long enough. hci_send_to_sock() invokes the filter before hci_event_packet() validates the event header. A malformed event supplied by a controller or a vhci device can therefore cause an out-of-bounds read. Keep the unmasked event code for the opcode checks. The masked value is needed for the 64-bit event bitmap, but using it to identify command events aliases event codes above 0x3f. In particular, Synchronous Train Complete (0x4f) was treated as Command Status (0x0f) even though its payload has no opcode. Reject actual command events that are too short for the field being inspected. A truncated command event cannot match a configured opcode.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th 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.2%
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.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 39e99d85071bca0feeec3164a9437ca1bff297fcaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before ebdd49cec380731844ed9df4092a29a014623df4affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2501a3b7b7144d1d11939b355a48ed01f83d0c62affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before dca25c204f71be0556a15177dbe037237ac43e5eaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 3976bbcd43b9b94c53ac9b0fd28888011588f4ccaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before f894f6292d5122cd62d30600736b4a0ae79f7770affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1a92763c2ba721bf113cd83f913fe8c511b4a4dcaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b0a6cf99afd57a39598b1beca0e86ef5004980deaffected · git
- before 2.6.12not 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-98459Oct 18, 2026 · Bluetooth: ISO: balance the parent hold in hci_bind_bis()0Monitor
- ← EarlierCVE-2026-98460Oct 18, 2026 · Bluetooth: hci_sock: reject out-of-range OCF values0Monitor
- Later →CVE-2026-98462Oct 18, 2026 · Bluetooth: hci_conn: fix CIS hold ownership on reuse0Monitor
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 | 1a92763c2ba721bf113cd83f913fe8c511b4a4dc | Vendor (CNA) |
| Linux Linux | 2501a3b7b7144d1d11939b355a48ed01f83d0c62 | Vendor (CNA) |
| Linux Linux | 3976bbcd43b9b94c53ac9b0fd28888011588f4cc | Vendor (CNA) |
| Linux Linux | 39e99d85071bca0feeec3164a9437ca1bff297fc | Vendor (CNA) |
| Linux Linux | b0a6cf99afd57a39598b1beca0e86ef5004980de | Vendor (CNA) |
| Linux Linux | dca25c204f71be0556a15177dbe037237ac43e5e | Vendor (CNA) |
| Linux Linux | ebdd49cec380731844ed9df4092a29a014623df4 | Vendor (CNA) |
| Linux Linux | f894f6292d5122cd62d30600736b4a0ae79f7770 | 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 3, 2026+15 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/2501a3b7b7144d1d11939b355a48ed01f83d0c62
- git.kernel.org/stable/c/3976bbcd43b9b94c53ac9b0fd28888011588f4cc
- git.kernel.org/stable/c/39e99d85071bca0feeec3164a9437ca1bff297fc
- git.kernel.org/stable/c/b0a6cf99afd57a39598b1beca0e86ef5004980de
- git.kernel.org/stable/c/dca25c204f71be0556a15177dbe037237ac43e5e
- git.kernel.org/stable/c/ebdd49cec380731844ed9df4092a29a014623df4
- git.kernel.org/stable/c/f894f6292d5122cd62d30600736b4a0ae79f7770
Vendor advisories and official records. Exploit/PoC links are deliberately left out.