Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2025-39737

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup() A soft lockup warning was observed on a relative small system x86-64…

Published Sep 11, 2025CWE-401EPSS 0.18%

Overview

CVE-2025-39737 is a medium-severity vulnerability. It was published on September 11, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

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

mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()

A soft lockup warning was observed on a relative small system x86-64

system with 16 GB of memory when running a debug kernel with kmemleak

enabled.

watchdog: BUG: soft lockup - CPU#8 stuck for 33s! [kworker/8:1:134]

The test system was running a workload with hot unplug happening in

parallel. Then kemleak decided to disable itself due to its inability to

allocate more kmemleak objects. The debug kernel has its

CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE set to 40,000.

The soft lockup happened in kmemleak_do_cleanup() when the existing

kmemleak objects were being removed and deleted one-by-one in a loop via a

workqueue. In this particular case, there are at least 40,000 objects

that need to be processed and given the slowness of a debug kernel and the

fact that a raw_spinlock has to be acquired and released in

__delete_object(), it could take a while to properl

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/1ef72a7fedc5bca70e8cc980985790de10d407aaRefgit.kernel.org/stable/c/8d2d22a55ffe35c38e69795468a7addd1a80e9ceRefgit.kernel.org/stable/c/926092268efdf1ed7b55cf486356c74a9e7710d1Refgit.kernel.org/stable/c/9b80430c194e4a114dc663c1025d56b4f3d0153dRefgit.kernel.org/stable/c/9f1f4e95031f84867c5821540466d62f88dab8caRefgit.kernel.org/stable/c/a04de4c40aab9b338dfa989cf4aec70fd187eeb2Refgit.kernel.org/stable/c/d1534ae23c2b6be350c8ab060803fbf6e9682adcRefgit.kernel.org/stable/c/e21a3ddd58733ce31afcb1e5dc3cb80a4b5bc29bRefgit.kernel.org/stable/c/f014c10d190b92aad366e56b445daffcd1c075e4Reflists.debian.org/debian-lts-announce/2025/10/msg00007.html

How CyberStrike helps

Frequently asked questions

What is CVE-2025-39737?

CVE-2025-39737 is a medium-severity vulnerability. It was published on September 11, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2025-39737?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-39737?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-39737?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-39737 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2025

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999