CVE-2026-23299
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| sles | affected | | |
| debian | bookworm | fixed | 0 |
| debian | bullseye | fixed | 0 |
| debian | forky | fixed | 6.19.8-1 |
| debian | sid | fixed | 6.19.8-1 |
| debian | trixie | fixed | 0 |
| linux-kernel | affected | 6.18.17 | |
| linux-kernel | 7.0 | affected | |
References
- https://www.suse.com/security/cve/CVE-2026-23299.html
- https://security-tracker.debian.org/tracker/CVE-2026-23299
- https://git.kernel.org/stable/c/21e4271e65094172aadd5beb8caea95dd0fbf6d7
- https://git.kernel.org/stable/c/2b6c942a526635f5c61d2f000258e620da32d3a7
- https://git.kernel.org/stable/c/3de7c10a950b36affc692d8bd2ac713852580e56
CWEs
CWE-772
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.