CVE-2026-80823
nfc: st21nfca: validate ATR_REQ length against the received frame
Reported by linux · Published September 4, 2026
In the Linux kernel, the following vulnerability has been resolved: nfc: st21nfca: validate ATR_REQ length against the received frame st21nfca_tm_recv_atr_req() checks that the received ATR_REQ frame is at least ST21NFCA_ATR_REQ_MIN_SIZE and that the self-declared atr_req->length is at least sizeof(struct st21nfca_atr_req), but never checks that atr_req->length does not exceed the actual received length (skb->len). st21nfca_tm_send_atr_res() then trusts the declared length: gb_len = atr_req->length - sizeof(struct st21nfca_atr_req); ... memcpy(atr_res->gbi, atr_req->gbi, gb_len); so an RF peer that sends a short frame but sets atr_req->length larger than the frame makes gb_len exceed the general bytes actually present, and the memcpy reads out of bounds past the received skb. Those bytes are placed in the ATR_RES and sent back to the peer (kernel-memory disclosure to a proximity attacker); a larger declared length is an out-of-bounds read (DoS). Reject frames whose declared length exceeds the received length. The adjacent nfc_tm_activated() path in the same function already derives its general-bytes length from skb->len rather than the declared field. Found by 0sec (https://0sec.ai) using automated source analysis; the missing bound is evident from source. Compile-tested.
EPSS 0.19% · 9.3th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | f33cecf69095c43be88567fef92b180b858f7369, dd26d30f40c43ad9cfe2f25c6ea0ead1dd51d5aa, bfcca5f42c9aa4eadef1e5fe7bb23783d7fcc96d, 9635507fe82949e429b3cd938876a9917125b151, 785df00bb3ae3206674a43284eb06dac575b5c64, 5cdcca5d62a66eda6b774110a44cba67bc1a8d1d, 304f5b414f4051d324b8c4a3ab0e79f7dc7e150e, 2c1ad291f4cdc357f9527b688c6fda9c6ffa7890, 0f344944c506b4f02d2b098489f7268b438c369e |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1892bf844ea0261736bd5e75546fc996e9daeedf, 1892bf844ea0261736bd5e75546fc996e9daeedf, 1892bf844ea0261736bd5e75546fc996e9daeedf |
| Linux | Linux | 3.17, 0, 5.10.267 |
| Linux | Linux | 7.3, 0, 5.10.267 |
| linux | linux_kernel | 3.17, 3.17, 3.17 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (14 in total, the first dated here)
- Sep 15, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80823
vulnetix vdb fixes CVE-2026-80823
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80823/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart