Socket resource leak via missing ISO reference release
Published Oct 6, 2026 · Updated Oct 6, 2026
Bluetooth ISO socket leak in Linux 6.6.67 through 6.6.157 and 6.8 allows attackers to retain listener sockets when child allocation fails. In iso_conn_ready(), the iso_sock_alloc() failure path calls release_sock() but omits sock_put() for the reference acquired by iso_get_sock(). Triggering the leak requires an ISO listening socket and failed child allocation; the retained socket consumes kernel resources and can block Bluetooth module removal.
Summary
What happened
Bluetooth ISO socket leak in Linux 6.6.67 through 6.6.157 and 6.8 allows attackers to retain listener sockets when child allocation fails. In iso_conn_ready(), the iso_sock_alloc() failure path calls release_sock() but omits sock_put() for the reference acquired by iso_get_sock(). Triggering the leak requires an ISO listening socket and failed child allocation; the retained socket consumes kernel resources and can block Bluetooth module removal.
The record
- CVE
- CVE-2026-98293
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11dc486ed5d4626e6b92a23b67ed76cb6c48bfc9 <ea8a262662be62c095789924c11722ecbf40a4de
- Affected versionversion=6.6.67 <6.6.158
- Affected versionversion=6.8
- Affected versionversion=fa224d0c094a458e9ebf5ea9b1c696136b7af427 <9228f87365e68a6cae191f57f456e89a6d2167cf
- Affected versionversion=fa224d0c094a458e9ebf5ea9b1c696136b7af427 <ca18ee413a7cb6f09885778039225e58bae0d607
- Affected versionversion=fa224d0c094a458e9ebf5ea9b1c696136b7af427 <e2b156a8d25966be49c1f809b654a2c4bb16564d
- Affected versionversion=fa224d0c094a458e9ebf5ea9b1c696136b7af427 <f016daabd4fec4e9b8563f8b6f42eabce0ca66b0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started