CVE-2026-23299: Bluetooth: purge error queues in socket destructors
Noroxi assessment
Priority: Monitor (action score 22/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.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 21e4271e65094172aadd5beb8caea95dd0fbf6d7, 2b6c942a526635f5c61d2f000258e620da32d3a7, 3de7c10a950b36affc692d8bd2ac713852580e56.
Low priority for now. Upgrade to Linux Linux 21e4271e65094172aadd5beb8caea95dd0fbf6d7, 2b6c942a526635f5c61d2f000258e620da32d3a7, 3de7c10a950b36affc692d8bd2ac713852580e56 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: purge error queues in socket destructors When TX timestamping is enabled via SO_TIMESTAMPING, SKBs may be queued into sk_error_queue and will stay there until consumed. If userspace never gets to read the timestamps, or if the controller is removed unexpectedly, these SKBs will leak. Fix by adding skb_queue_purge() calls for sk_error_queue in affected bluetooth destructors. RFCOMM does not currently use sk_error_queue.
- Published
- Mar 25, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-772
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.15 and later · before 6.18.17
- linux linux kernel6.19 and later · before 6.19.7
- linux linux kernel7.0
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.15affected
- 134f4b39df7b77225a80ef585c15d46f964f5e6f and later · before 2b6c942a526635f5c61d2f000258e620da32d3a7affected · git
- 134f4b39df7b77225a80ef585c15d46f964f5e6f and later · before 3de7c10a950b36affc692d8bd2ac713852580e56affected · git
- 134f4b39df7b77225a80ef585c15d46f964f5e6f and later · before 21e4271e65094172aadd5beb8caea95dd0fbf6d7affected · git
- before 6.15not affected · semver
- 6.18.17 and later · up to and including 6.18.*not affected · semver
- 6.19.7 and later · up to and including 6.19.*not affected · semver
- 7.0 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 6.19.8-1 | 6.19.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23297Mar 25, 2026 · nfsd: Fix cred ref leak in nfsd_nl_threads_set_doit().22Monitor
- ← EarlierCVE-2026-23298Mar 25, 2026 · can: ucan: Fix infinite loop from zero-length messages22Monitor
- Later →CVE-2026-23301Mar 25, 2026 · ASoC: SDCA: Add allocation failure check for Entity name22Monitor
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 | 21e4271e65094172aadd5beb8caea95dd0fbf6d7 | Vendor (CNA) |
| Linux Linux | 2b6c942a526635f5c61d2f000258e620da32d3a7 | Vendor (CNA) |
| Linux Linux | 3de7c10a950b36affc692d8bd2ac713852580e56 | Vendor (CNA) |
| debian:linux | 6.19.8-1 · Debian:14 | 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.
No history yet (it accumulates with the daily EPSS job).
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.
- CVE-2026-64003116 days apartscsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues30Monitor
- CVE-2022-50189280 days aparttools/power turbostat: Fix file pointer leak28Monitor
- CVE-2025-7123235 days apartscsi: qla2xxx: Free sp in error path to fix system crash22Monitor
- CVE-2026-2321935 days apartmm/slab: Add alloc_tagging_slab_free_hook for memcg_alloc_abort_single22Monitor
- CVE-2026-4305437 days apartscsi: target: tcm_loop: Drain commands in target_reset handler22Monitor
- CVE-2026-4325742 days apartmedia: cx88: Add missing unmap in snd_cx88_hw_params()22Monitor
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
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-772 · Missing Release of Resource after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.