Skip to main content
Mallory
HighVulnerability

CVE-2025-37924: Linux ksmbd Kerberos Authentication Use-After-Free

Published May 20, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS24.5%98th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Debian ProjectLinux
IdentifiersCVE-2025-37924CWE-416 · Use After Free

CVE-2025-37924 is a use-after-free race condition in the Linux kernel ksmbd server's Kerberos authentication session handling. During user-object teardown, a session's user pointer can be passed to the user-freeing routine before the pointer is cleared. A concurrent thread operating on the same session can dereference that pointer during this interval, accessing freed memory.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause use-after-free memory corruption in kernel-space ksmbd processing. The supplied information does not establish a specific, reliable outcome such as kernel code execution, privilege escalation, or denial of service, but such outcomes are generally possible consequences of kernel memory-safety flaws depending on exploitability.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround is available. Until patched, disable ksmbd where it is not required, restrict SMB service exposure to trusted networks and authenticated clients, and limit use of Kerberos-authenticated ksmbd sessions.

Remediation

Patch, then assume compromise.

Update to a Linux kernel version containing the fix for CVE-2025-37924. For affected VMware Tanzu Ubuntu Jammy stemcells, deploy the vendor-provided 1.1282.x fixed stemcell release applicable to the environment.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2025-37924 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2025-37924 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-37924?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2025-37924.
Is there a patch for CVE-2025-37924?
Update to a Linux kernel version containing the fix for CVE-2025-37924. For affected VMware Tanzu Ubuntu Jammy stemcells, deploy the vendor-provided 1.1282.x fixed stemcell release applicable to the environment.
What products are affected by CVE-2025-37924?
Linux Kernel and Debian Project Debian Linux.
How severe is CVE-2025-37924?
CVE-2025-37924 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 24.5% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.