CVE-2025-37947

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-05-20. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2025-15903 (ENISA EUVD) · GHSA-c42x-xw5m-9j9p (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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

ksmbd: prevent out-of-bounds stream writes by validating *pos

ksmbd_vfs_stream_write() did not validate whether the write offset (*pos) was within the bounds of the existing stream data length (v_len). If *pos was greater than or equal to v_len, this could lead to an out-of-bounds memory write.

This patch adds a check to ensure *pos is less than v_len before proceeding. If the condition fails, -EINVAL is returned.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.7%
EPSS %ILE
52nd
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

May 20, 2025

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Jul 30, 2026
Patch available.
Web page

KSMBD-CVE-2025-37947/CVE-2025-37947.c at main · doyensec/KSMBD-CVE-2025-37947 · GitHub

https://github.com/doyensec/KSMBD-CVE-2025-37947/blob/main/CVE-2025-37947.c
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4271-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/08/msg00010.html
Web page

ksmbd: prevent out-of-bounds stream writes by validating *pos - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: prevent out-of-bounds stream writes by validating *pos - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: prevent out-of-bounds stream writes by validating *pos - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7f61da79df86fd140c7768e668ad846bfa7ec8e1
Web page

ksmbd: prevent out-of-bounds stream writes by validating *pos - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ca6df4f40cf4c32487944aaf48319cb6c25accc
Web page

ksmbd: prevent out-of-bounds stream writes by validating *pos - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04c8a38c60346bb5a7c49b276de7233f703ce9cb

Vendor Advisories for CVE-2025-37947(1)

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

Patch Availability(19)

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.137-1~deb11u1 (8 versions)
  • every version up to 6.1.140-1~deb11u1: fixed in 6.1.140-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (40 versions)
  • every version up to 6.1.140-1: fixed in 6.1.140-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.29-1: fixed in 6.12.29-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.29-1: fixed in 6.12.29-1
—

Additional Vendor Advisories

(19)

Frequently asked(5)

What is CVE-2025-37947?
CVE-2025-37947 is a high-severity vulnerability; its CVE record was published on May 20, 2025. In the Linux kernel, the following vulnerability has been resolved: ksmbd: prevent out-of-bounds stream writes by validating *pos ksmbd_vfs_stream_write() did not validate whether the write offset (*pos) was within the bounds of the existing stream data length (v_len). If *pos was greater than or…
When was the CVE record for CVE-2025-37947 published?
The CVE record for CVE-2025-37947 was published on May 20, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-37947 actively exploited?
CVE-2025-37947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-37947?
CVE-2025-37947 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-37947?
A fix for CVE-2025-37947 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-37947 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-37947

Explore →

Is Your Infrastructure Affected by CVE-2025-37947?

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