CVE-2026-74300: Bluetooth: hci: validate codec capability element length
Noroxi assessment
Priority: Monitor (action score 35/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.40% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 290b36f9d1eb9b2f72b40d826f26b4a182ab15f7, 4bc16db0f11918e07edf9fdcda4a30cf4c9df45c, c38fbcdc407925c7088f7e5f11c1fff73d2d35a2.
Low priority for now. Upgrade to Linux Linux 290b36f9d1eb9b2f72b40d826f26b4a182ab15f7, 4bc16db0f11918e07edf9fdcda4a30cf4c9df45c, c38fbcdc407925c7088f7e5f11c1fff73d2d35a2 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: validate codec capability element length Read Local Codec Capabilities returns a sequence of capability elements. Each element starts with a one-byte length followed by that many payload bytes. hci_read_codec_capabilities() checks that the skb contains the length byte, but then validates only caps->len against the remaining skb length. A malformed controller response with one remaining byte and caps->len set to one passes that check even though the element needs two bytes. The parser then records a two-byte capability and copies one byte beyond the advertised response payload into the codec list. Validate the full element size, including the length byte, before adding it to the accumulated capability length. This preserves all well-formed capability elements and drops only truncated controller responses.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- —
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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
- 5.16affected
- 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and later · before fc97fc8cf7f53fd3619db63e09050d20a3a0c4b1affected · git
- 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and later · before 290b36f9d1eb9b2f72b40d826f26b4a182ab15f7affected · git
- 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and later · before f2ad01f55e07f9531efcea736087e6b8658a3440affected · git
- 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and later · before ec4d352747a62c1082f16c11a74b37d6eb85a5a3affected · git
- 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and later · before 4bc16db0f11918e07edf9fdcda4a30cf4c9df45caffected · git
- 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and later · before c38fbcdc407925c7088f7e5f11c1fff73d2d35a2affected · git
- before 5.16not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-74296Aug 15, 2026 · RDMA/mlx5: Release the HW‑provided UAR index rather than the SW one31Monitor
- ← EarlierCVE-2026-74297Aug 15, 2026 · RDMA/mlx5: Fix undefined shift of user RQ WQE size31Monitor
- Later →CVE-2026-74302Aug 15, 2026 · Bluetooth: hci_core: Fix UAF in hci_unregister_dev()31Monitor
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 | 290b36f9d1eb9b2f72b40d826f26b4a182ab15f7 | Vendor (CNA) |
| Linux Linux | 4bc16db0f11918e07edf9fdcda4a30cf4c9df45c | Vendor (CNA) |
| Linux Linux | c38fbcdc407925c7088f7e5f11c1fff73d2d35a2 | Vendor (CNA) |
| Linux Linux | ec4d352747a62c1082f16c11a74b37d6eb85a5a3 | Vendor (CNA) |
| Linux Linux | f2ad01f55e07f9531efcea736087e6b8658a3440 | Vendor (CNA) |
| Linux Linux | fc97fc8cf7f53fd3619db63e09050d20a3a0c4b1 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4bc16db0f11918e07edf9fdcda4a30cf4c9df45c
- git.kernel.org/stable/c/c38fbcdc407925c7088f7e5f11c1fff73d2d35a2
- git.kernel.org/stable/c/ec4d352747a62c1082f16c11a74b37d6eb85a5a3
- git.kernel.org/stable/c/f2ad01f55e07f9531efcea736087e6b8658a3440
- git.kernel.org/stable/c/fc97fc8cf7f53fd3619db63e09050d20a3a0c4b1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.