CVE-2026-31622
Last modified
CVE-2026-31622 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: NFC: digital: Bounds check NFC-A cascade depth in SDD response handler The NFC-A anti-collision cascade in digital_in_recv_sdd_res() appends 3 or 4 bytes to target->nfcid1 on each round, but the number of cascade rounds is controlled entirely by the peer device. The peer sets the cascade tag in the SDD_RES (deciding 3 vs 4 bytes) and the cascade-incomplete bit in the SEL_RES (deciding whether another round follows). ISO 14443-3 limits NFC-A to three cascade levels and target->nfcid1 is sized accordingly (NFC_NFCID1_MAXSIZE = 10), but nothing in the driver actually enforces this. EPSS estimates a 0.28% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: NFC: digital: Bounds check NFC-A cascade depth in SDD response handler The NFC-A anti-collision cascade in digital_in_recv_sdd_res() appends 3 or 4 bytes to target->nfcid1 on each round, but the number of cascade rounds is controlled entirely by the peer device. The peer sets the cascade tag in the SDD_RES (deciding 3 vs 4 bytes) and the cascade-incomplete bit in the SEL_RES (deciding whether another round follows). ISO 14443-3 limits NFC-A to three cascade levels and target->nfcid1 is sized accordingly (NFC_NFCID1_MAXSIZE = 10), but nothing in the driver actually enforces this. This means a malicious peer can keep the cascade running, writing past the heap-allocated nfc_target with each round. Fix this by rejecting the response when the accumulated UID would exceed the buffer. Commit e329e71013c9 ("NFC: nci: Bounds check struct nfc_target arrays") fixed similar missing checks against the same field on the NCI path.
Metrics
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 3.13, < 6.6.136 |
| Linux | Linux Kernel | >= 6.7, < 6.12.83 |
| Linux | Linux Kernel | >= 6.13, < 6.18.24 |
| Linux | Linux Kernel | >= 6.19, < 6.19.14 |
| Linux | Linux Kernel | >= 7.0, < 7.0.1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-31622?
How severe is CVE-2026-31622?
How do I fix CVE-2026-31622?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-31616In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31617In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31618In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31619In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31620In the Linux kernel, the following vulnerability has been re…4.6
- CVE-2026-31621In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31623In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31624In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31625In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-31626In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-31627In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-31628In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-31622?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
