CVE-2026-31622: NFC: digital: Bounds check NFC-A cascade depth in SDD response handler

Published Apr 24, 2026
·
Updated

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 digitalinrecvsddres() 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 SDDRES (deciding 3 vs 4 bytes) and the cascade-incomplete bit in the SELRES (deciding whether another round follows).

ISO 14443-3 limits NFC-A to three cascade levels and target->nfcid1 is sized accordingly (NFCNFCID1MAXSIZE = 10), but nothing in the driver actually enforces this. This means a malicious peer can keep the cascade running, writing past the heap-allocated nfctarget with each round.

Fix this by rejecting the response when the accumulated UID would exceed the buffer.

Commit e329e71013c9 ("NFC: nci: Bounds check struct nfctarget arrays") fixed similar missing checks against the same field on the NCI path.

Affected Software

8 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.134.1-2
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
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.12-1Fixed in 7.2.15-1
  2. Compensating control

    In the NFC-A SDD response handler, reject the response when the accumulated UID would exceed the target->nfcid1 buffer, enforcing the NFC_NFCID1_MAXSIZE = 10 limit and preventing cascade processing beyond three cascade levels.

Event History

Apr 24, 2026
CVE Published
via MITRE·02:42 PM
Data Sourced
via MITRE·02:42 PM
DescriptionSeverity
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 26, 2026
Data Sourced
via Microsoft·08:09 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-31622?

CVE-2026-31622 has a severity rating that indicates potential risks associated with the bounds check failure in the NFC-A cascade depth.

2

How do I fix CVE-2026-31622?

To fix CVE-2026-31622, update the Linux kernel to the latest version where the vulnerability has been addressed.

3

Which versions of the Linux kernel are affected by CVE-2026-31622?

CVE-2026-31622 affects certain versions of the Linux kernel that do not include the necessary bounds checks in the NFC-A cascade.

4

What impact does CVE-2026-31622 have on system security?

CVE-2026-31622 can lead to vulnerabilities that may allow an attacker to exploit the NFC-A cascade response, potentially leading to information exposure.

5

Is CVE-2026-31622 related to user data security?

Yes, CVE-2026-31622 can pose risks to user data security due to improper handling of NFC-A communications.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203