CVE-2026-31709

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
44
EG Risk 44/100

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%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

Published

May 1, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated May 3, 2026
Patch available.
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(10)

Vendor / EcosystemFix (by version range) / 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
linuxKernel @ 5.15.210 (fixes >=5.12.0)—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 rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)
  • every version up to 6.12.86-1: fixed in 6.12.86-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.1-1~exp1 (133 versions)
  • every version up to 7.0.3-1: fixed in 7.0.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(16)

Data Freshness Timeline

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

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

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 on May 1, 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-31709 actively exploited?
CVE-2026-31709 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-31709?
CVE-2026-31709 has a CVSS base score of 8.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-31709?
A fix for CVE-2026-31709 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-31709 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.