# CVE-2026-98575: nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()

> A malicious NFC device can trigger an out-of-bounds read in the Linux kernel pn533 driver, potentially leaking memory or causing a crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108927, BELL-CVE-2026-98575, DEBIAN-CVE-2026-98575, GHSA-68mj-7vm5-9gjg, UBUNTU-CVE-2026-98575

## What is CVE-2026-98575?

CVE-2026-98575 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()

frame->ccid.datalen is read directly from the USB response frame
and used, unchecked, as an index into frame->data[]. A malicious or
malfunctioning device can set this field to an arbitrary value,
causing the driver to read far outside the received buffer.

Bound ccid.datalen against the maximum possible ACR122 frame size
before using it. This replaces the existing datalen == 0 check,
since datalen < 2 already covers that case and additionally
rejects datalen == 1, which would still underflow the
"datalen - 2" offset used below.

## Which versions are affected by CVE-2026-98575?


## How do I fix CVE-2026-98575?

Apply the vendor's patch.

## Is CVE-2026-98575 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98575 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-98575 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-98575/ (Markdown: https://insights.sbomify.com/CVE-2026-98575/index.md)
```

## Sources

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

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