CVE-2026-90225 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, as well as users and distributors of Linux-based systems, should assess exposure and apply the available patch. Linux kernel developers and maintainers should review and apply the patch to prevent potential exploitation. Users and distributors of Linux-based systems should also review their systems for potential exposure and apply the patch as needed. Additionally, system administrators and security teams should be

Why it matters

A race condition vulnerability in the Linux kernel's NFC LLCP implementation could allow a local attacker to potentially access sensitive information or cause a denial of service. Linux kernel developers and maintainers, as well as users and distributors of Linux-based systems, should assess exposure and apply the available patch.

• Local attackers could potentially access sensitive information or cause a denial of service
• System crashes or instability may occur due to the use-after-free or unexpected behavior

Technical summary

The vulnerability exists in the `nfc_llcp_getsockopt()` function, which reads the `llcp_sock->local` pointer before acquiring the socket lock. If a `bind()` operation is racing with the `getsockopt()` call, the `llcp_sock->local` pointer could be freed or mutated, leading to a use-after-free or unexpected behavior. This could allow a local attacker to potentially access sensitive information or cause a denial of service. Linux kernel developers and maintainers should assess exposure and apply the available patch. The vulnerability is caused by a race condition in the `nfc_llcp_getsockopt()` function. The function reads the `llcp_sock->local` pointer before acquiring the socket lock, which can lead to a use-

Defensive priority

High

Recommended defensive actions

• Review and apply the available patch to the Linux kernel
• Restrict access to the vulnerable component
• Monitor system logs for potential exploitation attempts
• Perform a thorough review of system configurations and network architecture to identify potential vulnerabilities
• Implement compensating controls, such as firewalls or intrusion detection systems, to detect and prevent exploitation
• Conduct a thorough asset inventory to identify affected systems and prioritize remediation efforts
• Establish a rollback/change management process to quickly respond to potential security incidents

Evidence notes

The vulnerability is caused by a race condition in the `nfc_llcp_getsockopt()` function. The function reads the `llcp_sock->local` pointer before acquiring the socket lock, which can lead to a use-after-free or unexpected behavior if a `bind()` operation is racing with the `getsockopt()` call.

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.