CVE-2026-98247
Bluetooth: hci_codec: validate vendor codec count length
No known exploitation. EPSS puts it in the 10th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 8961987f3f5fa2f2618e72304d013c8dd5e604a6, < 9c04b9a4d08b95dee901d24b7607c4cbd65fa0a8Upgrade to: 9c04b9a4d08b95dee901d24b7607c4cbd65fa0a8Affected: ≥ 8961987f3f5fa2f2618e72304d013c8dd5e604a6, < a6da782fefae611e68a1aa79644065fc8ca5abcdUpgrade to: a6da782fefae611e68a1aa79644065fc8ca5abcdAffected: ≥ 8961987f3f5fa2f2618e72304d013c8dd5e604a6, < e4cfd3c4299105237458b27958bd7b0aa4c60795Upgrade to: e4cfd3c4299105237458b27958bd7b0aa4c60795Affected: ≥ 8961987f3f5fa2f2618e72304d013c8dd5e604a6, < f49a543d76d48f184b34225d9c0e2fc4cbdea8ecUpgrade to: f49a543d76d48f184b34225d9c0e2fc4cbdea8ec + 2 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_codec: validate vendor codec count length The Read Local Supported Codecs parsers consume the variable-sized standard codec array before parsing the vendor codec count. Although the initial reply-size check includes a vendor count byte in the fixed layout, it does not guarantee that the byte remains after the standard codec array. If a controller reply ends immediately after that array, calculating the vendor codec array size reads vnd_codecs->num beyond the skb data. Use skb_pull_data() to validate and consume each codec header before using its count in both command variants.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 10th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/9c04b9a4d08b95dee901d24b7607c4cbd65fa0a8
- git.kernel.org/stable/c/a6da782fefae611e68a1aa79644065fc8ca5abcd
- git.kernel.org/stable/c/e4cfd3c4299105237458b27958bd7b0aa4c60795
And 3 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI