PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-99015 Linux CVE debrief

A Linux kernel vulnerability allows for a potential NULL pointer dereference or use-after-free when rebinding an HCI socket after its controller is unregistered. This issue arises from a race condition between the `hci_sock_bind` function and the `send_monitor_control_replay` function. The vulnerability has been resolved through a series of commits that ensure proper serialization of dead-device detachment.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-23
Original CVE updated
2026-10-30
Advisory published
2026-10-23
Advisory updated
2026-10-30

Who should care

Linux kernel developers, maintainers, and users who rely on Bluetooth HCI sockets should assess their exposure to this vulnerability and apply patches or mitigations as needed. This includes operators managing Linux kernel deployments, platform administrators, vulnerability management teams, and security teams responsible for monitoring and mitigating potential threats.

Why it matters

This vulnerability requires attention from Linux kernel developers, maintainers, and users who rely on Bluetooth HCI sockets. Patches have been provided to resolve the issue, and users should verify their exposure and apply mitigations as needed.

  • Potential NULL pointer dereference or use-after-free
  • Race condition between hci_sock_bind and send_monitor_control_replay functions
  • Requires verification of HCI socket rebinding and detachment

Technical summary

The Linux kernel vulnerability CVE-2026-99015 is related to the Bluetooth HCI socket implementation. A race condition exists between the `hci_sock_bind` function and the `send_monitor_control_replay` function, which can lead to a NULL pointer dereference or use-after-free. The vulnerability has been resolved through a series of commits that ensure proper serialization of dead-device detachment. This issue requires attention from Linux kernel developers, maintainers, and users who rely on Bluetooth HCI sockets. Patches have been provided to resolve the issue, and users should verify their exposure and apply mitigations as needed.

Defensive priority

Medium

Recommended defensive actions

  • Review and apply patches from Linux kernel maintainers
  • Verify HCI socket rebinding and detachment in Linux kernel
  • Monitor Linux kernel updates for potential vulnerabilities
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to patches. However, there is limited information on potential exploits or attacks.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-99015 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-99015

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-99015 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-99015

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Bluetooth: hci_sock: Serialize dead-device detachment

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/99xxx/CVE-2026-99015.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/88f47e66b1a6e0bfc350676937f3b552b434e74c

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/304adbdb96b0491c2b377e216b0bf417fc8e69a9

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/362126f739889436048f5573ebc87466d2525fd9

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/37cef0c8fb537f40600910d2c2e5f2d5509305f3

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/76f2e2665697340ac719e7ff1bf148dd014e55c1

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/c3d2799877906d0c8392d96e14216cd82b020330

    Supplemental source

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/e660a22402944f2615a16fde7129a3c497537329

    Supplemental source

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.