CVE-2026-90092 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, as well as users of Linux-based systems, should assess their exposure to this vulnerability and apply the provided patches to mitigate the risk.

Why it matters

This vulnerability in the Linux kernel's Bluetooth L2CAP implementation can lead to a use-after-free condition, potentially allowing attackers to exploit the vulnerability. Linux kernel developers and maintainers, as well as users of Linux-based systems, should assess their exposure to this vulnerability and apply the provided patches to mitigate the risk.

• Verify kernel version and apply patches to prevent potential UAF exploitation
• Monitor system logs for potential exploitation attempts
• Review and update Linux kernel configurations to ensure secure implementation

Technical summary

The Linux kernel's Bluetooth L2CAP implementation is vulnerable to a use-after-free condition. This occurs when a new socket is added to the parent socket's accept queue after the parent socket has been closed, resulting in a dangling reference. The issue arises from a race condition between l2cap_sock_new_connection_cb() and l2cap_sock_teardown_cb(). Linux kernel developers and maintainers, as well as users of Linux-based systems, should assess their exposure to this vulnerability and apply the provided patches to mitigate the risk. The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the corpus does not establish versions, exploitation, impact,

Defensive priority

High

Recommended defensive actions

• Review and apply the provided kernel patches to address the vulnerability
• Ensure that the Linux kernel is updated to a version that includes the fix
• Monitor system logs for potential exploitation attempts
• Verify kernel version and apply patches to prevent potential UAF exploitation
• Review and update Linux kernel configurations to ensure secure implementation
• 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

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the corpus does not establish versions, exploitation, impact, or remediation, which require verification from the supplied official sources.

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.