CVE-2025-40099

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2025-10-30. A secondary CVSS source baseline 9.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 5 sources updated this week

Also known asEUVD-2025-36979 (ENISA EUVD) · GHSA-58x9-22gw-84q7 (GitHub Security Advisories)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

cifs: parse_dfs_referrals: prevent oob on malformed input

Malicious SMB server can send invalid reply to FSCTL_DFS_GET_REFERRALS

  • reply smaller than sizeof(struct get_dfs_referral_rsp)
  • reply with number of referrals smaller than NumberOfReferrals in the
header

Processing of such replies will cause oob.

Return -EINVAL error on such replies to prevent oob-s.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-05). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 30, 2025

Last Modified

October 19, 2026

Advisory Details (5)

Auto-updated Oct 2, 2026
Patch available.
Web page

cifs: parse_dfs_referrals: prevent oob on malformed input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6447b0e355562a1ff748c4a2ffb89aae7e84d2c9
Web page

cifs: parse_dfs_referrals: prevent oob on malformed input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb0f2e66e1ac043a5b238f5bcab4f26f3c317039
Web page

cifs: parse_dfs_referrals: prevent oob on malformed input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8bc4a8d39bac23d8b044fd3e2dbfd965f1d9b058
Web page

cifs: parse_dfs_referrals: prevent oob on malformed input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15c73964da9df994302f579ed14ee5fdbce7a332
Web page

cifs: parse_dfs_referrals: prevent oob on malformed input - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cfacc7441f760e4a73cc71b6ff1635261d534657

Vendor Advisories for CVE-2025-40099(2)

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

Patch Availability(16)

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1 ... 6.1.153-1~deb11u1 (12 versions)
  • every version up to 6.1.158-1~deb11u1: fixed in 6.1.158-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (44 versions)
  • every version up to 6.1.158-1: fixed in 6.1.158-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.57-1~bpo12+1 (6 versions)
  • every version up to 6.12.57-1: fixed in 6.12.57-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.5-1~exp1 (75 versions)
  • every version up to 6.17.6-1: fixed in 6.17.6-1
—

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 26× in last 7d / 111× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 301 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 201 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-40099?
CVE-2025-40099 is a critical-severity vulnerability; its CVE record was published on October 30, 2025. In the Linux kernel, the following vulnerability has been resolved: cifs: parse_dfs_referrals: prevent oob on malformed input Malicious SMB server can send invalid reply to FSCTL_DFS_GET_REFERRALS reply smaller than sizeof(struct get_dfs_referral_rsp) reply with number of referrals smaller than…
When was the CVE record for CVE-2025-40099 published?
The CVE record for CVE-2025-40099 was published on October 30, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-40099 actively exploited?
CVE-2025-40099 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-40099?
CVE-2025-40099 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-40099?
A fix for CVE-2025-40099 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-40099 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-2025-40099

Explore →

Is Your Infrastructure Affected by CVE-2025-40099?

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