NFC: digital: Bounds check NFC-A cascade depth in SDD response handler
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.258, 5.15.209, 6.1.175, 6.12.83, 6.18.24, 6.19.14, 6.6.136, 7.0.1
- CVEs
- CVE-2026-31622
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 17:39 UTC · Revision 1
Source evidence
NFC: digital: Bounds check NFC-A cascade depth in SDD response handler
core-osv · Original sourcePublished 24 Apr 2026, 14:42 UTC
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.
osv:CVE-2026-31622
Kernel
Fixed versions: 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1
Complete source record
{
"id": "261ce7f5456e88290a6ede967b9d06720dce070ab06cd602ef0749bc0023ca27",
"url": "https://osv.dev/vulnerability/CVE-2026-31622",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "NFC: digital: Bounds check NFC-A cascade depth in SDD response handler",
"summary": "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.",
"evidence": "osv:CVE-2026-31622",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.258",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.209",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.175",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.136",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.83",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.24",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.14",
"evidence": "/affected/1/ranges"
},
{
"value": "7.0.1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-31622",
"aliases": [
"CVE-2026-31622"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2c66daecc4092e6049673c281b2e6f0d5e59a94c"
},
{
"fixed": "9ba6bb09e00b922d902f684f575779e5433fe6e3"
},
{
"fixed": "f83b399aa05a0712e3b1569a30d3d90b3533d2ef"
},
{
"fixed": "20663102c14566e900e1d2f679e30b7f1694f387"
},
{
"fixed": "2819f34e08bdffb6f06a51c67948ec5737fb166a"
},
{
"fixed": "1bec5698b55aa2be5c3b983dba657c01d0fd3dbc"
},
{
"fixed": "5a59bf70c38ee1eb4be03bab830bbc3a6f0bd1f1"
},
{
"fixed": "8d9d9bf3565271ca7ab9c716a94e87296177e7ba"
},
{
"fixed": "cc024a3de265ef6c58957f4990eccb9f806208cb"
},
{
"fixed": "46ce8be2ced389bccd84bcc04a12cf2f4d0c22d1"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31622.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.13.0"
},
{
"fixed": "5.10.258"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.209"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.175"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.136"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.83"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.24"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.14"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.20.0"
},
{
"fixed": "7.0.1"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-31622.json"
}
}
],
"modified": "2026-10-28T02:30:44.824963759Z",
"provider": "osv",
"references": [
"https://cert-portal.siemens.com/productcert/html/ssa-784472.html",
"https://git.kernel.org/stable/c/1bec5698b55aa2be5c3b983dba657c01d0fd3dbc",
"https://git.kernel.org/stable/c/20663102c14566e900e1d2f679e30b7f1694f387",
"https://git.kernel.org/stable/c/2819f34e08bdffb6f06a51c67948ec5737fb166a",
"https://git.kernel.org/stable/c/46ce8be2ced389bccd84bcc04a12cf2f4d0c22d1",
"https://git.kernel.org/stable/c/5a59bf70c38ee1eb4be03bab830bbc3a6f0bd1f1",
"https://git.kernel.org/stable/c/8d9d9bf3565271ca7ab9c716a94e87296177e7ba",
"https://git.kernel.org/stable/c/9ba6bb09e00b922d902f684f575779e5433fe6e3",
"https://git.kernel.org/stable/c/cc024a3de265ef6c58957f4990eccb9f806208cb",
"https://git.kernel.org/stable/c/f83b399aa05a0712e3b1569a30d3d90b3533d2ef",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31622.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-31622",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/31xxx/CVE-2026-31622.json"
}
},
"related_cves": [
{
"value": "CVE-2026-31622",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 512556,
"published_at": "2026-04-24T14:42:39.916+00:00"
}