CVE-2026-31614

HIGHCVSS · not yet scored7.1
EchelonGraph scoreLOW confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-04-24.

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

smb: client: fix off-by-8 bounds check in check_wsl_eas()

The bounds check uses (u8 *)ea + nlen + 1 + vlen as the end of the EA name and value, but ea_data sits at offset sizeof(struct smb2_file_full_ea_info) = 8 from ea, not at offset 0. The strncmp() later reads ea->ea_data[0..nlen-1] and the value bytes follow at ea_data[nlen+1..nlen+vlen], so the actual end is ea->ea_data + nlen + 1 + vlen. Isn't pointer math fun?

The earlier check (u8 *)ea > end - sizeof(*ea) only guarantees the 8-byte header is in bounds, but since the last EA is placed within 8 bytes of the end of the response, the name and value bytes are read past the end of iov.

Fix this mess all up by using ea->ea_data as the base for the bounds check.

An "untrusted" server can use this to leak up to 8 bytes of kernel heap into the EA name comparison and influence which WSL xattr the data is interpreted as.

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

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (6)

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

smb: client: fix off-by-8 bounds check in check_wsl_eas() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: fix off-by-8 bounds check in check_wsl_eas() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: fix off-by-8 bounds check in check_wsl_eas() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: fix off-by-8 bounds check in check_wsl_eas() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: fix off-by-8 bounds check in check_wsl_eas() - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: fix off-by-8 bounds check in check_wsl_eas() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d8b9d06bd3ac4c6846f5498800b0f5f8062e53b

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.6.136—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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 42× 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 136 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(4)

What is CVE-2026-31614?
CVE-2026-31614 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: client: fix off-by-8 bounds check in checkwsleas() The bounds check uses (u8 *)ea + nlen + 1 + vlen as the end of the EA name and value, but ea_data sits at offset sizeof(struct smb2filefulleainfo) = 8 from ea, not at offset…
When was CVE-2026-31614 disclosed?
CVE-2026-31614 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-31614 actively exploited?
CVE-2026-31614 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 97.4% of all scored CVEs.
How do I remediate CVE-2026-31614?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31614, 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-31614

Explore →

Is Your Infrastructure Affected by CVE-2026-31614?

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

Start Free Scan →Browse All CVEs