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

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

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102015, BELL-CVE-2026-90225, DEBIAN-CVE-2026-90225, GHSA-jphp-9f5v-q6mv, UBUNTU-CVE-2026-90225

## 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.

## Is CVE-2026-90225 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90225 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-90225 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90225/ (Markdown: https://insights.sbomify.com/CVE-2026-90225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90225
- OSV: https://osv.dev/vulnerability/CVE-2026-90225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90225/
Summaries are generated and may contain mistakes; the official description above is the record.