cve.bz

CVE-2025-39736 Improper Locking

5.5 mediumEPSS 0.1%Fix available

Medium (5.5). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid deadlock by moving pr_warn() outside kmemleak_lock When netpoll is enabled, calling pr_warn_once() while holding kmemleak_lock in mem_pool_alloc() can cause a deadlock due to lock inversion with the netconsole subsystem. This occurs because pr_warn_once() may trigger netpoll, which eventually leads to __alloc_skb() and back into kmemleak code, attempting to reacquire kmemleak_lock. This is the path for the deadlock. mem_pool_alloc() -> raw_spin_lock_irqsave(&kmemleak_lock, flags); -> pr_warn_once() -> netconsole subsystem -> netpoll -> __alloc_skb -> __create_object -> raw_spin_lock_irqsave(&kmemleak_lock, flags); Fix this by setting a flag and issuing the pr_warn_once() after kmemleak_lock is released.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-667 Improper Locking
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-39736 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-39736?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-39736?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-39736 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.4 and later

Fixed in

ProductRelease lineFixed in
Linux5.45.4.297
Linux5.105.10.241
Linux5.155.15.190
Linux6.16.1.149
Linux6.66.6.103
Linux6.126.12.43
Linux6.156.15.11
Linux6.166.16.2
Linuxlater releases6.17

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux5.10.244-1DLA-4327-1
Debian11linux-6.16.1.153-1~deb11u1DLA-4328-1
Debian12linux6.1.153-1DEBIAN-CVE-2025-39736 DSA-6009-1
Debian13linux6.12.43-1DEBIAN-CVE-2025-39736
Debian14linux6.16.3-1DEBIAN-CVE-2025-39736
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-39736
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-39736
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-39736
Ubuntu22.04:LTSlinux, linux-lowlatency5.15.0-163.173UBUNTU-CVE-2025-39736 USN-7909-1
Ubuntu22.04:LTSlinux-aws5.15.0-1097.104UBUNTU-CVE-2025-39736 USN-7909-1
Ubuntu22.04:LTSlinux-aws-6.8, linux-nvidia-6.86.8.0-1046.49~22.04.1UBUNTU-CVE-2025-39736 USN-8028-5
Ubuntu22.04:LTSlinux-azure5.15.0-1101.110UBUNTU-CVE-2025-39736 USN-7910-2
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1051.57~22.04.1UBUNTU-CVE-2025-39736 USN-8126-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1102.111.1UBUNTU-CVE-2025-39736
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1046.53~22.04.1UBUNTU-CVE-2025-39736
Ubuntu22.04:LTSlinux-gcp5.15.0-1097.106UBUNTU-CVE-2025-39736 USN-7909-4
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1047.50~22.04.2UBUNTU-CVE-2025-39736 USN-8031-1
60 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernel6.6.104.2-1AZL-67172
Alpaquita23linux-lts6.1.151-r0BELL-CVE-2025-39736
Alpaquita25linux-lts6.12.44-r0BELL-CVE-2025-39736
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-39736

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Low.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-39736.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-134-10Siemens SIMATIC2026-05-12Critical ManufacturingSIMATIC CN 4100none listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-25 Forced Deadlock Likelihood: Low · Severity: High
  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON