CVE-2026-31611

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: NoneExposed: 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: require 3 sub-authorities before reading sub_auth[2]

parse_dacl() compares each ACE SID against sid_unix_NFS_mode and on match reads sid.sub_auth[2] as the file mode. If sid_unix_NFS_mode is the prefix S-1-5-88-3 with num_subauth = 2 then compare_sids() compares only min(num_subauth, 2) sub-authorities so a client SID with num_subauth = 2 and sub_auth = {88, 3} will match.

If num_subauth = 2 and the ACE is placed at the very end of the security descriptor, sub_auth[2] will be 4 bytes past end_of_acl. The out-of-band bytes will then be masked to the low 9 bits and applied as the file's POSIX mode, probably not something that is good to have happen.

Fix this up by forcing the SID to actually carry a third sub-authority before reading it at all.

CVSS v3
8.6
EG Score
8.6(medium)
EPSS
28.8%
KEV
Not listed

Published

April 24, 2026

Last Modified

June 14, 2026

Advisory Details (6)

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

ksmbd: require 3 sub-authorities before reading sub_auth[2] - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: require 3 sub-authorities before reading sub_auth[2] - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: require 3 sub-authorities before reading sub_auth[2] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9401f86a224f37b50e6a3ccf1d46a70d5ef8af0a
generic

ksmbd: require 3 sub-authorities before reading sub_auth[2] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53370cf9090777774e07fd9a8ebce67c6cc333ab
generic

ksmbd: require 3 sub-authorities before reading sub_auth[2] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46bbcd3ebfb3549c8da1838fc4493e79bd3241e7
generic

ksmbd: require 3 sub-authorities before reading sub_auth[2] - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08f9e6d899b5c834bbcc239eae1bed58d9b15d2c

Vendor Advisories for CVE-2026-31611(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-31611?
CVE-2026-31611 is a high vulnerability published on April 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: require 3 sub-authorities before reading sub_auth[2] parsedacl() compares each ACE SID against sidunixNFSmode and on match reads sid.subauth[2] as the file mode. If sidunixNFSmode is the prefix S-1-5-88-3 with numsubauth = 2…
When was CVE-2026-31611 disclosed?
CVE-2026-31611 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-31611 actively exploited?
CVE-2026-31611 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31611?
CVE-2026-31611 has a CVSS v4.0 base score of 8.6 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-31611?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31611, 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-31611

Explore →

Is Your Infrastructure Affected by CVE-2026-31611?

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