# CVE-2026-98481: nfc: port100: reject frames whose declared length exceeds the received data

> A malicious NFC device can trigger an out-of-bounds read in the Linux kernel port100 driver by declaring a frame length larger than the actual received data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108668, BELL-CVE-2026-98481, DEBIAN-CVE-2026-98481, GHSA-76wj-ccjf-8q4p, UBUNTU-CVE-2026-98481

## What is CVE-2026-98481?

CVE-2026-98481 is a memory corruption vulnerability in Linux, published on 18 Oct 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: port100: reject frames whose declared length exceeds the received data

port100_recv_response() passes the URB transfer buffer to
port100_rx_frame_is_valid(), which checksums le16_to_cpu(frame->datalen)
bytes of frame->data. datalen is a 16-bit field supplied by the device
and is never checked against the number of bytes actually received
(urb->actual_length), so a device reporting a datalen larger than the
received frame makes port100_data_checksum() read out of bounds past the
transfer buffer.

Reject a response whose declared frame size does not fit the received
length before validating it.

Found by 0sec (https://0sec.ai) using automated source analysis; the
missing bound is evident from source. Compile-tested.

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


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

Apply the vendor's patch.

## Is CVE-2026-98481 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98481 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98481 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-98481/ (Markdown: https://insights.sbomify.com/CVE-2026-98481/index.md)
```

## Sources

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

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