In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: read llcp_sock->local under the socket lock in getsockopt… (CVE-2026-90225)
A high-severity vulnerability in the Linux kernel's NFC LLCP socket implementation was resolved. The flaw involved a race condition where getsockopt() could read and dereference a pointer after it was freed due to improper locking around llcp_sock->local. This could lead to use-after-free conditions causing potential confidentiality, integrity, and availability impacts.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-90225) in the Linux kernel NFC LLCP socket code was caused by nfc_llcp_getsockopt() reading the llcp_sock->local pointer before acquiring the socket lock, then dereferencing it inside the locked region. Meanwhile, llcp_sock_bind() modifies and frees this pointer under the socket lock. A race between getsockopt() and bind() could cause getsockopt() to dereference a freed pointer, leading to use-after-free. The fix moves the pointer read and null check inside the socket lock to prevent concurrent mutation or freeing during use.
Potential Impact
This vulnerability can lead to use-after-free conditions, potentially allowing attackers with local privileges to cause kernel memory corruption. The CVSS score of 7.8 indicates high impact on confidentiality, integrity, and availability. Exploitation could result in privilege escalation or denial of service.
Mitigation Recommendations
A fix has been implemented in the Linux kernel that moves the pointer read and null check inside the socket lock to prevent race conditions. Users should apply the official kernel updates that include this patch. No additional mitigations are indicated.
In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: read llcp_sock->local under the socket lock in getsockopt… (CVE-2026-90225)
Description
A high-severity vulnerability in the Linux kernel's NFC LLCP socket implementation was resolved. The flaw involved a race condition where getsockopt() could read and dereference a pointer after it was freed due to improper locking around llcp_sock->local. This could lead to use-after-free conditions causing potential confidentiality, integrity, and availability impacts.
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-90225) in the Linux kernel NFC LLCP socket code was caused by nfc_llcp_getsockopt() reading the llcp_sock->local pointer before acquiring the socket lock, then dereferencing it inside the locked region. Meanwhile, llcp_sock_bind() modifies and frees this pointer under the socket lock. A race between getsockopt() and bind() could cause getsockopt() to dereference a freed pointer, leading to use-after-free. The fix moves the pointer read and null check inside the socket lock to prevent concurrent mutation or freeing during use.
Potential Impact
This vulnerability can lead to use-after-free conditions, potentially allowing attackers with local privileges to cause kernel memory corruption. The CVSS score of 7.8 indicates high impact on confidentiality, integrity, and availability. Exploitation could result in privilege escalation or denial of service.
Mitigation Recommendations
A fix has been implemented in the Linux kernel that moves the pointer read and null check inside the socket lock to prevent race conditions. Users should apply the official kernel updates that include this patch. No additional mitigations are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jphp-9f5v-q6mv
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-90225"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aade52255bf5e2cf5edc187
Added to database: 09/19/2026, 01:28:02 UTC
Last enriched: 09/19/2026, 01:50:32 UTC
Last updated: 09/19/2026, 03:41:28 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.