CVE-2026-90256 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Bluetooth protocol implementers, and organizations deploying Linux-based systems with Bluetooth capabilities should assess their exposure and prioritize patching.

Why it matters

CVE-2026-90256 is a high-severity use-after-free vulnerability in the Linux kernel's Bluetooth L2CAP protocol. Defenders should assess exposure, prioritize patching, and monitor for potential exploitation attempts. The vulnerability requires verification of Linux kernel versions and Bluetooth L2CAP protocol usage to determine exposure. Remediation efforts should focus on applying patches from Linux kernel maintainers and ensuring proper locking mechanisms are in place.

• Potential use-after-free exploitation attempts require monitoring and incident response readiness.
• Verification of Linux kernel versions and Bluetooth L2CAP protocol usage is necessary to determine exposure.
• Patching and updating Linux kernel deployments to resolve the vulnerability is a high-priority defensive task.
• Remediation efforts should focus on applying patches from Linux kernel maintainers and ensuring proper locking mechanisms are in place.

Technical summary

The Linux kernel's Bluetooth L2CAP protocol is vulnerable to a use-after-free condition. The `hci_conn::l2cap_data` is accessed without proper locking in `l2cap_disconn_ind` via `hci_conn_timeout`. This can lead to a use-after-free if `l2cap_conn` is deleted concurrently. The vulnerability is resolved by using `proto_lock` to guard `l2cap_data`, in addition to `hdev->lock` which is held in other access paths.

Defensive priority

High-priority assessment and patching recommended for Linux kernel deployments with Bluetooth L2CAP protocol in use.

Recommended defensive actions

• Assess Linux kernel deployments for Bluetooth L2CAP protocol usage
• Verify and apply patches from Linux kernel maintainers
• Monitor for potential use-after-free exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 8.8 and HIGH severity. Two source references from the Linux kernel Git repository are provided. The vulnerability requires verification of Linux kernel versions and Bluetooth L2CAP protocol usage to determine exposure. Defenders should assess their exposure, prioritize patching, and monitor for potential exploitation attempts. The official CVE Program record and NVD detail page offer source-provided CVE metadata and vulnerability assessment.

Sources and references

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.