CVE-2025-22039

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-04-16. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

ksmbd: fix overflow in dacloffset bounds check

The dacloffset field was originally typed as int and used in an unchecked addition, which could overflow and bypass the existing bounds check in both smb_check_perm_dacl() and smb_inherit_dacl().

This could result in out-of-bounds memory access and a kernel crash when dereferencing the DACL pointer.

This patch converts dacloffset to unsigned int and uses check_add_overflow() to validate access to the DACL.

CVSS v3
7.1
EG Score
7.1(medium)
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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

April 16, 2025

Last Modified

September 14, 2026

Advisory Details (4)

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

ksmbd: fix overflow in dacloffset bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix overflow in dacloffset bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b8d379048b168a0dff5ab1acb975b933f368514
generic

ksmbd: fix overflow in dacloffset bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a9cd9ff0fa2bcc30b2bfb8bdb161eb20e44b9dc
generic

ksmbd: fix overflow in dacloffset bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/443b373a4df5a2cb9f7b8c4658b2afedeb16397f

Vendor Advisories for CVE-2025-22039(1)

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

Patch Availability(18)

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.25-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.25-1

Weakness Classification(2)

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

All Vendor Advisories

(18)

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2025-22039?
CVE-2025-22039 is a high vulnerability published on April 16, 2025. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix overflow in dacloffset bounds check The dacloffset field was originally typed as int and used in an unchecked addition, which could overflow and bypass the existing bounds check in both smbcheckpermdacl() and…
When was CVE-2025-22039 disclosed?
CVE-2025-22039 was first published in the National Vulnerability Database on April 16, 2025, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-22039 actively exploited?
CVE-2025-22039 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 45.8% of all scored CVEs.
What is the CVSS score of CVE-2025-22039?
CVE-2025-22039 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-22039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-22039, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-22039

Explore →

Is Your Infrastructure Affected by CVE-2025-22039?

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