CVE-2026-31622
published 2026-04-24CVE-2026-31622: 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…
PriorityP347high8.8CVSS 3.1
AVAACLPRNUINSUCHIHAH
EPSS
0.28%
20.1th percentile
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.
Affected
23 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| linux | linux | — | — |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < 9ba6bb09e00b922d902f684f575779e5433fe6e3 | 9ba6bb09e00b922d902f684f575779e5433fe6e3 |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < f83b399aa05a0712e3b1569a30d3d90b3533d2ef | f83b399aa05a0712e3b1569a30d3d90b3533d2ef |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < 20663102c14566e900e1d2f679e30b7f1694f387 | 20663102c14566e900e1d2f679e30b7f1694f387 |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < 2819f34e08bdffb6f06a51c67948ec5737fb166a | 2819f34e08bdffb6f06a51c67948ec5737fb166a |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < 1bec5698b55aa2be5c3b983dba657c01d0fd3dbc | 1bec5698b55aa2be5c3b983dba657c01d0fd3dbc |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < 5a59bf70c38ee1eb4be03bab830bbc3a6f0bd1f1 | 5a59bf70c38ee1eb4be03bab830bbc3a6f0bd1f1 |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < 8d9d9bf3565271ca7ab9c716a94e87296177e7ba | 8d9d9bf3565271ca7ab9c716a94e87296177e7ba |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < cc024a3de265ef6c58957f4990eccb9f806208cb | cc024a3de265ef6c58957f4990eccb9f806208cb |
| linux | linux | >= 2c66daecc4092e6049673c281b2e6f0d5e59a94c < 46ce8be2ced389bccd84bcc04a12cf2f4d0c22d1 | 46ce8be2ced389bccd84bcc04a12cf2f4d0c22d1 |
| linux | linux_kernel | >= 3.13 < 6.6.136 | 6.6.136 |
| linux | linux_kernel | >= 6.13 < 6.18.24 | 6.18.24 |
| linux | linux_kernel | >= 6.19 < 6.19.14 | 6.19.14 |
| linux | linux_kernel | >= 6.7 < 6.12.83 | 6.12.83 |
| linux | linux_kernel | >= 7.0 < 7.0.1 | 7.0.1 |
| ubuntu | linux | — | — |
| ubuntu | linux-aws | — | — |
| ubuntu | linux-gcp | — | — |
| ubuntu | linux-ibm | — | — |
| ubuntu | linux-nvidia | — | — |
| ubuntu | linux-oracle | — | — |
| ubuntu | linux-raspi | — | — |
| ubuntu | linux-realtime | — | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_ubuntu2.0LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Linux kernel (NVIDIA) vulnerabilities
vendor_ubuntu·2026-07-06·CVSS 2.0
CVE-2026-46009 [LOW] Linux kernel (NVIDIA) vulnerabilities
Title: Linux kernel (NVIDIA) vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM64 architecture;
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Rados block device (RBD) driver;
- Compressed RAM block device driver;
- Character device driver;
- TPM device driver;
- Hardware crypto device drivers;
- EDAC drivers;
- GPU drivers;
- Greybus drive
Ubuntu
Linux kernel (Raspberry Pi) vulnerabilities
vendor_ubuntu·2026-07-02·CVSS 2.0
CVE-2026-46316 [LOW] Linux kernel (Raspberry Pi) vulnerabilities
Title: Linux kernel (Raspberry Pi) vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM64 architecture;
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Rados block device (RBD) driver;
- Compressed RAM block device driver;
- Character device driver;
- TPM device driver;
- Hardware crypto device drivers;
- EDAC drivers;
- GPU drivers;
- Greybus
Ubuntu
Linux kernel vulnerabilities
vendor_ubuntu·2026-07-01·CVSS 2.0
CVE-2026-46042 [LOW] Linux kernel vulnerabilities
Title: Linux kernel vulnerabilities
Summary: Several security issues were fixed in the Linux kernel.
It was discovered that some AMD processors did not properly clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
- ARM64 architecture;
- x86 architecture;
- Block layer subsystem;
- Cryptographic API;
- Rados block device (RBD) driver;
- Compressed RAM block device driver;
- Character device driver;
- TPM device driver;
- Hardware crypto device drivers;
- EDAC drivers;
- GPU drivers;
- Greybus drivers;
- HID
Red Hat
kernel: NFC: digital: Bounds check NFC-A cascade depth in SDD response handler
vendor_redhat·2026-04-24
CVE-2026-31622 CWE-120 kernel: NFC: digital: Bounds check NFC-A cascade depth in SDD response handler
kernel: NFC: digital: Bounds check NFC-A cascade depth in SDD response handler
A flaw was found in the Linux kernel's NFC (Near Field Communication) digital subsystem. A malicious peer device can exploit this vulnerability by sending specially crafted NFC-A anti-collision cascade responses. This allows the peer to exceed the intended cascade depth, leading to a heap overflow by writing past the allocated buffer for the nfc_target. This memory corruption can result in a denial of service or potentially arbitrary code execution.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Not affected
Package: kernel-rt (Red Hat Enterprise Linux 7) - Not affected
Package: kernel (
GHSA
GHSA-3r85-565g-4jhq: 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
ghsa_unreviewed·2026-04-24
CVE-2026-31622 GHSA-3r85-565g-4jhq: 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
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 th
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/1bec5698b55aa2be5c3b983dba657c01d0fd3dbchttps://git.kernel.org/stable/c/20663102c14566e900e1d2f679e30b7f1694f387https://git.kernel.org/stable/c/2819f34e08bdffb6f06a51c67948ec5737fb166ahttps://git.kernel.org/stable/c/46ce8be2ced389bccd84bcc04a12cf2f4d0c22d1https://git.kernel.org/stable/c/5a59bf70c38ee1eb4be03bab830bbc3a6f0bd1f1https://git.kernel.org/stable/c/8d9d9bf3565271ca7ab9c716a94e87296177e7bahttps://git.kernel.org/stable/c/9ba6bb09e00b922d902f684f575779e5433fe6e3https://git.kernel.org/stable/c/cc024a3de265ef6c58957f4990eccb9f806208cbhttps://git.kernel.org/stable/c/f83b399aa05a0712e3b1569a30d3d90b3533d2ef
2026-04-24
Published