CVE-2026-31433

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 8.8; sources differ by 0.0.

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

ksmbd: fix potencial OOB in get_file_all_info() for compound requests

When a compound request consists of QUERY_DIRECTORY + QUERY_INFO (FILE_ALL_INFORMATION) and the first command consumes nearly the entire max_trans_size, get_file_all_info() would blindly call smbConvertToUTF16() with PATH_MAX, causing out-of-bounds write beyond the response buffer. In get_file_all_info(), there was a missing validation check for the client-provided OutputBufferLength before copying the filename into FileName field of the smb2_file_all_info structure. If the filename length exceeds the available buffer space, it could lead to potential buffer overflows or memory corruption during smbConvertToUTF16 conversion. This calculating the actual free buffer size using smb2_calc_max_out_buf_len() and returning -EINVAL if the buffer is insufficient and updating smbConvertToUTF16 to use the actual filename length (clamped by PATH_MAX) to ensure a safe copy operation.

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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

April 22, 2026

Last Modified

May 22, 2026

Advisory Details (7)

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

ksmbd: fix potencial OOB in get_file_all_info() for compound requests - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix potencial OOB in get_file_all_info() for compound requests - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix potencial OOB in get_file_all_info() for compound requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9d7032851d6f5adbe2739601ca456c0ad3b422f0
generic

ksmbd: fix potencial OOB in get_file_all_info() for compound requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7aec5a769d2356cbf344d85bcfd36de592ac96a5
generic

ksmbd: fix potencial OOB in get_file_all_info() for compound requests - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix potencial OOB in get_file_all_info() for compound requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a852f9d1c981fb14f6bf4e24999e0ea8088a7d7
generic

ksmbd: fix potencial OOB in get_file_all_info() for compound requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/358cdaa1f7fbf2712cb4c5f6b59cb9a5c673c5fe

Vendor Advisories for CVE-2026-31433(1)

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.15.203osv

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

Frequently asked(5)

What is CVE-2026-31433?
CVE-2026-31433 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix potencial OOB in getfileall_info() for compound requests When a compound request consists of QUERYDIRECTORY + QUERYINFO (FILEALLINFORMATION) and the first command consumes nearly the entire maxtranssize,…
When was CVE-2026-31433 disclosed?
CVE-2026-31433 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on May 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31433 actively exploited?
CVE-2026-31433 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.8% of all scored CVEs.
What is the CVSS score of CVE-2026-31433?
CVE-2026-31433 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-31433?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31433, 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-31433

Explore →

Is Your Infrastructure Affected by CVE-2026-31433?

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