CVE-2026-31622

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-24. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (6)

Auto-updated May 2, 2026
No patch confirmed yet.
generic

NFC: digital: Bounds check NFC-A cascade depth in SDD response handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc024a3de265ef6c58957f4990eccb9f806208cb
generic

NFC: digital: Bounds check NFC-A cascade depth in SDD response handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d9d9bf3565271ca7ab9c716a94e87296177e7ba
generic

NFC: digital: Bounds check NFC-A cascade depth in SDD response handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a59bf70c38ee1eb4be03bab830bbc3a6f0bd1f1
generic

NFC: digital: Bounds check NFC-A cascade depth in SDD response handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46ce8be2ced389bccd84bcc04a12cf2f4d0c22d1
generic

NFC: digital: Bounds check NFC-A cascade depth in SDD response handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2819f34e08bdffb6f06a51c67948ec5737fb166a
generic

NFC: digital: Bounds check NFC-A cascade depth in SDD response handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1bec5698b55aa2be5c3b983dba657c01d0fd3dbc

Vendor Advisories for CVE-2026-31622(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.258osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 44× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-07-28 15:36 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-25 14:17 UTCEPSS rescore
  6. 2026-07-24 14:17 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 03:08 UTCEG score recompute
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-20 13:34 UTCOSV refresh
  17. 2026-07-19 14:31 UTCEPSS rescore
  18. 2026-07-19 14:31 UTCEPSS rescore
  19. 2026-07-19 02:29 UTCEPSS rescore
  20. 2026-07-18 10:04 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-16 17:03 UTCEPSS rescore
  23. 2026-07-16 17:03 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 75 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
  26. 2026-06-25 13:49 UTCEPSS rescore
  27. 2026-06-24 14:05 UTCEPSS rescore
  28. 2026-06-23 21:33 UTCEPSS rescore
  29. 2026-06-23 21:33 UTCEPSS rescore
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-22 14:25 UTCEPSS rescore
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 14:56 UTCEPSS rescore
  34. 2026-06-21 01:59 UTCEPSS rescore
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-19 19:25 UTCEPSS rescore
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-18 17:52 UTCEPSS rescore
  39. 2026-06-17 17:53 UTCEPSS rescore
  40. 2026-06-16 17:52 UTCEPSS rescore
  41. 2026-06-15 17:49 UTCEPSS rescore
  42. 2026-06-14 23:23 UTCVendor advisory
  43. 2026-06-14 23:23 UTCGHSA enrichment
  44. 2026-06-14 23:18 UTCEPSS rescore
  45. 2026-06-14 11:52 UTCVendor advisory
  46. 2026-06-14 11:52 UTCGHSA enrichment
  47. 2026-06-13 23:00 UTCEPSS rescore
  48. 2026-06-12 23:12 UTCEPSS rescore
  49. 2026-06-12 23:12 UTCEPSS rescore
  50. 2026-06-12 01:31 UTCVendor advisory
  51. 2026-06-12 01:31 UTCGHSA enrichment
  52. 2026-06-11 14:00 UTCVendor advisory
  53. 2026-06-11 14:00 UTCGHSA enrichment
  54. 2026-06-11 14:00 UTCEPSS rescore
  55. 2026-06-10 22:56 UTCGHSA enrichment
  56. 2026-06-10 22:18 UTCEPSS rescore
  57. 2026-06-10 13:22 UTCEPSS rescore
  58. 2026-06-10 11:24 UTCVendor advisory
  59. 2026-06-10 11:24 UTCGHSA enrichment
  60. 2026-06-09 23:53 UTCVendor advisory
  61. 2026-06-09 23:53 UTCGHSA enrichment
  62. 2026-06-09 12:22 UTCVendor advisory
  63. 2026-06-09 12:22 UTCGHSA enrichment
  64. 2026-06-09 00:45 UTCVendor advisory
  65. 2026-06-09 00:45 UTCGHSA enrichment
  66. 2026-06-08 14:17 UTCEPSS rescore
  67. 2026-06-08 14:17 UTCEPSS rescore
  68. 2026-06-08 09:02 UTCVendor advisory
  69. 2026-06-08 09:02 UTCGHSA enrichment
  70. 2026-06-07 21:32 UTCVendor advisory
  71. 2026-06-07 21:32 UTCGHSA enrichment
  72. 2026-06-07 15:25 UTCEPSS rescore
  73. 2026-06-07 15:25 UTCEPSS rescore
  74. 2026-06-07 15:25 UTCEPSS rescore
  75. 2026-06-07 10:00 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-31622?
CVE-2026-31622 is a high vulnerability published on April 24, 2026. 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…
When was CVE-2026-31622 disclosed?
CVE-2026-31622 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31622 actively exploited?
CVE-2026-31622 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.6% of all scored CVEs.
What is the CVSS score of CVE-2026-31622?
CVE-2026-31622 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31622?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31622, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-31622

Explore →

Is Your Infrastructure Affected by CVE-2026-31622?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.