BlackTreeIndependent security intelligence

Full vulnerability report · 2025

CVE-2025-39737High confidence

mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

21 package states

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`linux`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gke`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gkeop`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-ibm`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-intel`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-lowlatency`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-nvidia-tegra`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-xilinx`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 8 Sept 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current

SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0

1 known affected

The vendor explicitly identifies these products as affected by this CVE.

SIMATIC CN 4100

Summary: 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 properly handle all these objects. As kmemleak has been disabled in this case, the object removal and deletion process can be further optimized as locking isn't really needed. However, it is probably not worth the effort to optimize for such an edge case that should rarely happen. So the simple solution is to call cond_resched() at periodic interval in the iteration loop to avoid soft lockup.
Remediation: Update to V5.0 or later version

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2025-28974

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

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 properly handle all these objects. As kmemleak has been disabled in this case, the object removal and deletion process can be further optimized as locking isn't really needed. However, it is probably not worth the effort to optimize for such an edge case that should rarely happen. So the simple solution is to call cond_resched() at periodic interval in the iteration loop to avoid soft lockup.

What

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → Missing Release of Memory after Effective Lifetime → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-401 ↗
CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

CWE-401

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-28974Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2025-2040Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Sicherheitsmechanismen zu umgehen, sowie einen Denial of Service Angriff oder andere nicht spezifizierte Angriffe durchzuführen.

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0565Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39756 https://www.cve.org/CVERecord?id=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0246Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39720 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39739 https://www.cve.org/CVERecord?id=CVE-2025-39739 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39744 https://www.cve.org/CVERecord?id=CVE-2025-39744 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0227Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0194Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory

CERT-FR · French · CERTFR-2026-AVI-0169Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1135Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39728 https://www.cve.org/CVERecord?id=CVE-2025-39728 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39735 https://www.cve.org/CVERecord?id=CVE-2025-39735 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39756 https://www.cve.org/CVERecord?id=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1075Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-39724 Référence CVE CVE-2025-39725 https://www.cve.org/CVERecord?id=CVE-2025-39725 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39756 https://www.cve.org/CVERecord?id=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0894Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39756 https://www.cve.org/CVERecord?id=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0825Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39722 https://www.cve.org/CVERecord?id=CVE-2025-39722 Référence CVE CVE-2025-39723 https://www.cve.org/CVERecord?id=CVE-2025-39723 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39751 https://www.cve.org/CVERecord?id=CVE-2025-39751 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39756 https://www.cve.org/CVERecord?id=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=

Official advisory

NCSC-NL · Dutch · NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-producten

This Linux kernel update addresses multiple security vulnerabilities across various architectures and subsystems, including AMD CPU data leakage, SEV-SNP memory integrity flaws, VMSCAPE branch predictor isolation issues, and a soft lockup fix in kmemleak cleanup.

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: SIMATIC CN 4100
Fixed: < 5.4; 5.4.297 ≤ 5.4.*; 5.10.241 ≤ 5.10.*; 5.15.190 ≤ 5.15.*; 6.1.149 ≤ 6.1.*; 6.6.103 ≤ 6.6.*; 6.12.43 ≤ 6.12.*; 6.15.11 ≤ 6.15.*
Action: Update to V5.0 or later version
Workaround: No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.

Evidence and provenance

Published 11 Sept 2025 · Last source change 12 May 2026, 12:06 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2025-28974

Product sourceVendor CSAF · Siemens ProductCERT

Remediation sourceVendor CSAF · Siemens ProductCERT

CWE sourceNIST NVD

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2025-09-11CVE published

2026-05-12Fixed release or patch reference recorded

ENISA EUVD · EUVD-2025-28974↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2025-28974

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.