CVE-2026-31709

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

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

smb: client: validate the whole DACL before rewriting it in cifsacl

build_sec_desc() and id_mode_to_cifs_acl() derive a DACL pointer from a server-supplied dacloffset and then use the incoming ACL to rebuild the chmod/chown security descriptor.

The original fix only checked that the struct smb_acl header fits before reading dacl_ptr->size or dacl_ptr->num_aces. That avoids the immediate header-field OOB read, but the rewrite helpers still walk ACEs based on pdacl->num_aces with no structural validation of the incoming DACL body.

A malicious server can return a truncated DACL that still contains a header, claims one or more ACEs, and then drive replace_sids_and_copy_aces() or set_chmod_dacl() past the validated extent while they compare or copy attacker-controlled ACEs.

Factor the DACL structural checks into validate_dacl(), extend them to validate each ACE against the DACL bounds, and use the shared validator before the chmod/chown rebuild paths. parse_dacl() reuses the same validator so the read-side parser and write-side rewrite paths agree on what constitutes a well-formed incoming DACL.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
17.3%
KEV
Not listed

Published

May 1, 2026

Last Modified

June 30, 2026

Advisory Details (2)

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

smb: client: validate the whole DACL before rewriting it in cifsacl - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: client: validate the whole DACL before rewriting it in cifsacl - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0a8cf165566ba55a39fd0f4de172119dd646d39a

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-55.77.1.el10_02026-06-08redhat
redhatkernel-0:5.14.0-427.129.1.el9_42026-06-04redhat
redhatkernel-0:6.12.0-211.20.1.el10_22026-06-04redhat
redhatkernel-0:5.14.0-570.119.1.el9_62026-06-04redhat
redhatkernel-rt-0:5.14.0-284.174.1.rt14.459.el9_22026-06-03redhat
redhatkernel-0:5.14.0-284.174.1.el9_22026-06-03redhat
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat
redhatkernel-rt-0:4.18.0-553.126.1.rt7.467.el8_102026-05-28redhat
redhatkernel-0:4.18.0-553.126.1.el8_102026-05-28redhat

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 8× in last 7d / 83× 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 163 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31709?
CVE-2026-31709 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the whole DACL before rewriting it in cifsacl buildsecdesc() and idmodetocifsacl() derive a DACL pointer from a server-supplied dacloffset and then use the incoming ACL to rebuild the chmod/chown security…
When was CVE-2026-31709 disclosed?
CVE-2026-31709 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31709 actively exploited?
CVE-2026-31709 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31709?
CVE-2026-31709 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-31709?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31709, 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-31709

Explore →

Is Your Infrastructure Affected by CVE-2026-31709?

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