Strix
63.1K

CVE-2026-80823

Unknown

Last modified

CVE-2026-80823 is a vulnerability of currently unknown severity. 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.

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1892bf844ea0261736bd5e75546fc996e9daeedf, < 785df00bb3ae3206674a43284eb06dac575b5c64; >= 1892bf844ea0261736bd5e75546fc996e9daeedf, < 2c1ad291f4cdc357f9527b688c6fda9c6ffa7890; >= 1892bf844ea0261736bd5e75546fc996e9daeedf, < dd26d30f40c43ad9cfe2f25c6ea0ead1dd51d5aa; >= 1892bf844ea0261736bd5e75546fc996e9daeedf, < 9635507fe82949e429b3cd938876a9917125b151; >= 1892bf844ea0261736bd5e75546fc996e9daeedf, < 0f344944c506b4f02d2b098489f7268b438c369e; >= 1892bf844ea0261736bd5e75546fc996e9daeedf, < bfcca5f42c9aa4eadef1e5fe7bb23783d7fcc96d; >= 1892bf844ea0261736bd5e75546fc996e9daeedf, < 304f5b414f4051d324b8c4a3ab0e79f7dc7e150e; >= 1892bf844ea0261736bd5e75546fc996e9daeedf, < f33cecf69095c43be88567fef92b180b858f7369; >= 1892bf844ea0261736bd5e75546fc996e9daeedf, < 5cdcca5d62a66eda6b774110a44cba67bc1a8d1d
LinuxLinux3.17

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80823?
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.
How severe is CVE-2026-80823?
Severity scoring for CVE-2026-80823 is pending analysis.
How do I fix CVE-2026-80823?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80823?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST