Cloudanix VulnDB

CVE-2025-37962

None

CVSS

—

EPSS

0.2%

Published

May 20, 2025

CISA due date

—

Cloudanix analysis

Next patch cycle SSVC: Track

A bug in Linux file-sharing code can slowly waste memory when certain network requests arrive, which may eventually slow down or crash servers if left unfixed.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
Low
Impact
Denial Of Service
Component
OS kernel
Class
Memory Corruption
Remediation
Patch
Effort
Medium
Patch risk
Low

What it actually does

Memory leak in ksmbd parse_lease_state() where bounds check failure on create lease context returns NULL without freeing the previously allocated lease_ctx_info structure.

Why it matters to the business

Repeated triggering on Linux servers handling SMB traffic can gradually exhaust kernel memory, leading to performance degradation or service instability in high-connection environments; low urgency given low EPSS and no KEV listing.

How an attack unfolds

An attacker sends crafted SMB create requests containing lease contexts that fail the added bounds checks, causing parse_lease_state to leak the allocated lease_ctx_info on each failure; related Linux kernel privilege-escalation activity by threat actors has targeted similar ksmbd paths but no direct exploitation of this leak is recorded.

How to fix it

Upgrade the Linux kernel to the version containing commit facf22c1a394c1e023dab5daf9a494f722771e1c or later stable releases that include the kfree(lreq) fix in both boundary-check return paths.

How to confirm the fix worked

Confirm the applied kernel contains facf22c1a394c1e023dab5daf9a494f722771e1c; recompile or test with lease-context inputs that previously failed bounds checks and verify no leak occurs via memory accounting tools.

Typical attack path

  1. Establish SMB session to a vulnerable ksmbd server
  2. Send create request with lease context that violates bounds checks
  3. Trigger repeated allocation without free path
  4. Monitor for gradual kernel memory growth leading to resource exhaustion

How to detect it

Watch for sustained increases in kernel slab or ksmbd-related memory allocations correlated with SMB create/lease traffic; review system logs and memory profilers for patterns matching repeated parse_lease_state calls without corresponding frees.

What your security team should do

  • Prioritize kernel upgrade to facf22c1a394c1e023dab5daf9a494f722771e1c on all systems exposing ksmbd
  • Monitor kernel memory usage on SMB servers for unexpected growth
  • Disable ksmbd if SMB services are not required until patched
  • Track EPSS trend and any new threat-actor activity around related ksmbd CVEs

The record

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix memory leak in parse_lease_state() The previous patch that added bounds check for create lease context introduced a memory leak. When the bounds check fails, the function returns NULL without freeing the previously allocated lease_ctx_info structure. This patch fixes the issue by adding kfree(lreq) before returning NULL in both boundary check cases.

Affected packages

Ecosystem Package Introduced Fixed
Debian:11 linux-6.1 0 6.1.140-1~deb11u1
Debian:12 linux 0 6.1.140-1
Debian:13 linux 0 No fix
Debian:13 linux 0 6.12.29-1
Debian:14 linux 0 6.12.29-1
Linux Kernel 6.1.134 6.1.139
Mageia:9 dwarves 0 1.30-1.mga9
Mageia:9 kernel 0 6.6.93-1.mga9
Mageia:9 kernel-firmware 0 20250509-1.mga9
Mageia:9 kernel-firmware-nonfree 0 20250509-1.mga9.nonfree
Mageia:9 kernel-linus 0 6.6.93-1.mga9
Mageia:9 kmod-virtualbox 0 7.1.8-3.mga9
Mageia:9 kmod-xtables-addons 0 3.24-80.mga9
Mageia:9 libtraceevent 0 1.8.4-1.mga9
Mageia:9 libtracefs 0 1.8.2-1.mga9
Mageia:9 radeon-firmware 0 20250509-1.mga9.nonfree
Mageia:9 wireless-regdb 0 20250220-1.mga9

Related vulnerabilities