CVE-2026-31391

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-03. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

crypto: atmel-sha204a - Fix OOM ->tfm_count leak

If memory allocation fails, decrement ->tfm_count to avoid blocking future reads.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

April 3, 2026

Last Modified

September 8, 2026

Advisory Details (9)

Auto-updated Jul 16, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

crypto: atmel-sha204a - Fix OOM ->tfm_count leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: atmel-sha204a - Fix OOM ->tfm_count leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: atmel-sha204a - Fix OOM ->tfm_count leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: atmel-sha204a - Fix OOM ->tfm_count leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f502049a96b368ea6646c49d9520d6f69a101fa
generic

crypto: atmel-sha204a - Fix OOM ->tfm_count leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66ee9c1c3575b5d6afc340faca00fd40ed5b7ad9
generic

crypto: atmel-sha204a - Fix OOM ->tfm_count leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2bfc83cee05f8b9604502df27d94e8e2b4a3dbf1
generic

crypto: atmel-sha204a - Fix OOM ->tfm_count leak - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-31391(1)

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

Patch Availability(15)

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 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-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 (122 versions)6.19.10-1

All Vendor Advisories

(14)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-31391?
CVE-2026-31391 is a medium vulnerability published on April 3, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: atmel-sha204a - Fix OOM ->tfm_count leak If memory allocation fails, decrement ->tfm_count to avoid blocking future reads.
When was CVE-2026-31391 disclosed?
CVE-2026-31391 was first published in the National Vulnerability Database on April 3, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31391 actively exploited?
CVE-2026-31391 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 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-31391?
CVE-2026-31391 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31391?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31391, 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-31391

Explore →

Is Your Infrastructure Affected by CVE-2026-31391?

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