CVE-2026-98582 nfc: st21nfca: validate received frame size
A malformed NFC frame can cause out-of-bounds reads in the Linux kernel st21nfca driver, potentially leading to crashes or code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-98582?
CVE-2026-98582 is a memory corruption vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
nfc: st21nfca: validate received frame size
st21nfca_hci_i2c_repack() trims a received frame at its EOF marker before removing byte stuffing. It then assumes the truncated frame contains the LLC header and two CRC bytes, and it unconditionally reads the byte after an escape marker.
A malformed frame can place EOF immediately after the start marker or can end its data portion with an escape marker. The former leaves too few bytes for check_crc(), while the latter makes the unstuffing loop read past the current skb length.
Require the minimum framing bytes both before and after unstuffing. Use separate input and output cursors while removing byte stuffing, and reject an escape marker without its encoded byte. This keeps malformed frames within the received frame boundary before CRC processing.
Which versions are affected by CVE-2026-98582?
How do I fix CVE-2026-98582?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-98582 being exploited?
There is no known exploitation of CVE-2026-98582 in the wild and no public exploit code.
Sources
Also known as AZL-108969, BELL-CVE-2026-98582, DEBIAN-CVE-2026-98582, GHSA-g367-xhx5-qhm5, UBUNTU-CVE-2026-98582.