CVE-2026-31612

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: 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:

ksmbd: validate EaNameLength in smb2_get_ea()

smb2_get_ea() reads ea_req->EaNameLength from the client request and passes it directly to strncmp() as the comparison length without verifying that the length of the name really is the size of the input buffer received.

Fix this up by properly checking the size of the name based on the value received and the overall size of the request, to prevent a later strncmp() call to use the length as a "trusted" size of the buffer. Without this check, uninitialized heap values might be slowly leaked to the client.

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

Published

April 24, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Apr 29, 2026
No patch confirmed yet.
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66751841212c2cc196577453c37f7774ff363f02
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/551dfb15b182abad4600eaf7b37e6eb7000d5b1b
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b73376feecb3b61172fe5b4ff42bbbb8531669d
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3363a770b193f555f29d76ddf4ced3305c0ccf6d
generic

ksmbd: validate EaNameLength in smb2_get_ea() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/243b206bcb5a7137e8bddd57b2eec81e1ebd3859

Vendor Advisories for CVE-2026-31612(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 @ 6.1.175—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
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—

Additional Vendor Advisories

(18)

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

Frequently asked(5)

What is CVE-2026-31612?
CVE-2026-31612 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate EaNameLength in smb2getea() smb2getea() reads ea_req->EaNameLength from the client request and passes it directly to strncmp() as the comparison length without verifying that the length of the name really is the…
When was CVE-2026-31612 disclosed?
CVE-2026-31612 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-31612 actively exploited?
CVE-2026-31612 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 65.3% of all scored CVEs.
What is the CVSS score of CVE-2026-31612?
CVE-2026-31612 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31612?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31612, 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-31612

Explore →

Is Your Infrastructure Affected by CVE-2026-31612?

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

Start Free Scan →Browse All CVEs