Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.15, < 6.18.17 |
Related Weaknesses (CWE)
References
- https://git.kernel.org/stable/c/21e4271e65094172aadd5beb8caea95dd0fbf6d7Patch
- https://git.kernel.org/stable/c/2b6c942a526635f5c61d2f000258e620da32d3a7Patch
- https://git.kernel.org/stable/c/3de7c10a950b36affc692d8bd2ac713852580e56Patch
FAQ
What is CVE-2026-23299?
CVE-2026-23299 is a vulnerability with a CVSS score of 5.5 (MEDIUM). 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 s...
How severe is CVE-2026-23299?
CVE-2026-23299 has been rated MEDIUM with a CVSS base score of 5.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-23299?
Check the references section above for vendor advisories and patch information. Affected products include: Linux Linux Kernel.