# CVE-2026-80803: nfc: digital: clamp SENSF_RES length to the destination buffer

> A malicious NFC-F device can trigger a stack buffer overflow in the Linux kernel NFC driver, potentially leading to code execution or system 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:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-99399, BELL-CVE-2026-80803, DEBIAN-CVE-2026-80803, GHSA-p57f-2f7j-w542, UBUNTU-CVE-2026-80803

## What is CVE-2026-80803?

CVE-2026-80803 is a memory corruption vulnerability in Linux, published on 4 Sep 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: digital: clamp SENSF_RES length to the destination buffer

digital_in_recv_sensf_res() memcpy()s resp->len bytes from a remote
NFC-F device response into the NFC_SENSF_RES_MAXSIZE-byte target.sensf_res
field without an upper-bound check. A nearby malicious NFC-F device can
send an oversized SENSF_RES response to overflow the stack-local struct
nfc_target.

Clamp resp->len to NFC_SENSF_RES_MAXSIZE before the copy.

Found by 0sec automated security-research tooling (https://0sec.ai).

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


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

Apply the vendor's patch.

## Is CVE-2026-80803 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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