Shellfeed logo Shellfeed

CVE-2026-80823 · UNKNOWN

Summary: nfc: st21nfca: validate ATR_REQ length against the received frame

Details

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 packages

  • GIT git.kernel.org/pub/scm/linux/kernel/git/stable/linux [1892bf844ea0261736bd5e75546fc996e9daeedf – 785df00bb3ae3206674a43284eb06dac575b5c64]
  • Linux Kernel [3.17.0 – 5.10.267] [5.11.0 – 5.15.218] [5.16.0 – 6.1.185] [6.2.0 – 6.6.154] [6.7.0 – 6.12.106] [6.13.0 – 6.18.47] [6.19.0 – 7.1.11] [7.2.0 – 7.2.1]

References