CVE-2026-98293: Bluetooth: ISO: Fix parent socket leak in iso_conn_ready()
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 6.6.158, 9228f87365e68a6cae191f57f456e89a6d2167cf, ca18ee413a7cb6f09885778039225e58bae0d607; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 6.6.158, 9228f87365e68a6cae191f57f456e89a6d2167cf, ca18ee413a7cb6f09885778039225e58bae0d607; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: ISO: Fix parent socket leak in iso_conn_ready() iso_get_sock() returns the parent socket with a reference held, which is dropped by sock_put() once the child socket has been set up. The error path taken when iso_sock_alloc() fails only calls release_sock() and returns, leaking the reference and thus the parent socket itself. Drop the reference on that path as well.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th 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
- 6.8affected
- 11dc486ed5d4626e6b92a23b67ed76cb6c48bfc9 and later · before ea8a262662be62c095789924c11722ecbf40a4deaffected · git
- fa224d0c094a458e9ebf5ea9b1c696136b7af427 and later · before 9228f87365e68a6cae191f57f456e89a6d2167cfaffected · git
- fa224d0c094a458e9ebf5ea9b1c696136b7af427 and later · before e2b156a8d25966be49c1f809b654a2c4bb16564daffected · git
- fa224d0c094a458e9ebf5ea9b1c696136b7af427 and later · before f016daabd4fec4e9b8563f8b6f42eabce0ca66b0affected · git
- fa224d0c094a458e9ebf5ea9b1c696136b7af427 and later · before ca18ee413a7cb6f09885778039225e58bae0d607affected · git
- 6.6.67 and later · before 6.6.158affected · semver
- before 6.8not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
- 6.12.112 and later · up to and including 6.12.*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-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.8-1 | 7.2.8-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-98291Oct 6, 2026 · Bluetooth: btintel_pcie: fix off-by-one bounds check in RX submit0Monitor
- ← EarlierCVE-2026-98292Oct 6, 2026 · Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access0Monitor
- Later →CVE-2026-98294Oct 6, 2026 · Bluetooth: hci_qca: Do not write to the serial port after it is closed0Monitor
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 | 6.6.158 | Vendor (CNA) |
| Linux Linux | 9228f87365e68a6cae191f57f456e89a6d2167cf | Vendor (CNA) |
| Linux Linux | ca18ee413a7cb6f09885778039225e58bae0d607 | Vendor (CNA) |
| Linux Linux | e2b156a8d25966be49c1f809b654a2c4bb16564d | Vendor (CNA) |
| Linux Linux | ea8a262662be62c095789924c11722ecbf40a4de | Vendor (CNA) |
| Linux Linux | f016daabd4fec4e9b8563f8b6f42eabce0ca66b0 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | 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
- TodayOct 26, 2026+20 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).
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.