CVE-2026-90225 nfc: llcp: read llcp_sock->local under the socket lock in getsockopt

High 7.8 Published Updated

A race condition in the Linux kernel NFC LLCP module allows a use-after-free, potentially leading to code execution or denial of service.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-90225?

CVE-2026-90225 is a high-severity use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

In the Linux kernel, the following vulnerability has been resolved:

nfc: llcp: read llcp_sock->local under the socket lock in getsockopt

nfc_llcp_getsockopt() read llcp_sock->local before lock_sock(sk) and then dereferenced the cached pointer inside the locked region. llcp_sock_bind() assigns and clears llcp_sock->local under the same socket lock, dropping the last reference on its error path. A getsockopt() racing an in-flight bind() can observe the pointer, block on lock_sock(), and then dereference a freed nfc_llcp_local once bind() has unwound.

Move the llcp_sock->local read and the NULL check inside the lock_sock(sk) region so bind() cannot mutate or free the pointer between the load and the use.

Which versions are affected by CVE-2026-90225?

How do I fix CVE-2026-90225?

Apply the vendor's patch.

Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.

Is CVE-2026-90225 being exploited?

There is no known exploitation of CVE-2026-90225 in the wild and no public exploit code.

Sources

Also known as AZL-102015, BELL-CVE-2026-90225, DEBIAN-CVE-2026-90225, GHSA-jphp-9f5v-q6mv, UBUNTU-CVE-2026-90225.

Is CVE-2026-90225 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free