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

August 5, 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.258—osv

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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (126 versions)6.19.14-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 70× 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 259 total refreshes for this CVE.

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

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 August 5, 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.7% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs