BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2024-57951High confidence

hrtimers: Handle CPU state correctly on hotplug

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

19 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 releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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 feedCanonical record ↗Source updated 11 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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 feedCanonical record ↗Source updated 11 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.

2 current
SSA-265688 · CSAF 2.0 · revision 13 · interimSiemens ProductCERTSSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1
1 known affected

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

  • SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Summary
In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assumes that the hrtick is already active, and the chance of the clockevent device to transition to oneshot mode is also lost forever for the CPU, unless it goes back to a lower state than CPUHP_HRTIMERS_PREPARE once. This round-trip reveals another issue; cpu_base.online is not set to 1 after the transition, which appears as a WARN_ON_ONCE in enqueue_hrtimer(). Aside of that, the bulk of the per CPU state is not reset either, which means there are dangling pointers in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state and sets the online flag. [ tglx: Make the new callback unconditionally available, remove the online modification in the prepare() callback and clear the remaining state in the starting callback instead of the prepare callback ]
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-355557 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2
3 known affected

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

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assumes that the hrtick is already active, and the chance of the clockevent device to transition to oneshot mode is also lost forever for the CPU, unless it goes back to a lower state than CPUHP_HRTIMERS_PREPARE once. This round-trip reveals another issue; cpu_base.online is not set to 1 after the transition, which appears as a WARN_ON_ONCE in enqueue_hrtimer(). Aside of that, the bulk of the per CPU state is not reset either, which means there are dangling pointers in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state and sets the online flag.
Remediation
Update to V3.2 or later version
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-2024-53854

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assumes that the hrtick is already active, and the chance of the clockevent device to transition to oneshot mode is also lost forever for the CPU, unless it goes back to a lower state than CPUHP_HRTIMERS_PREPARE once. This round-trip reveals another issue; cpu_base.online is not set to 1 after the transition, which appears as a WARN_ON_ONCE in enqueue_hrtimer(). Aside of that, the bulk of the per CPU state is not reset either, which means there are dangling pointers in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state and sets the online flag. [ tglx: Make the new callback unconditionally available, remove the online modification in the prepare() callback and clear the remaining state in the starting callback instead of the prepare callback ]

What

In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assumes that the hrtick is already active, and the chance of the clockevent device to transition to oneshot mode is also lost forever for the CPU, unless it goes back to a lower state than CPUHP_HRTIMERS_PREPARE once. This round-trip reveals another issue; cpu_base.online is not set to 1 after the transition, which appears as a WARN_ON_ONCE in enqueue_hrtimer(). Aside of that, the bulk of the per CPU state is not reset either, which means there are dangling pointers in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state and sets the online flag. [ tglx: Make the new callback unconditionally available, remove the online modification in the prepare() callback and clear the remaining state in the starting callback instead of the prepare callback ]

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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

In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the online state, for instance CFS incorrectly assumes that the hrtick is already active, and the chance of the clockevent device to transition to oneshot mode is also lost forever for the CPU, unless it goes back to a lower state than CPUHP_HRTIMERS_PREPARE once. This round-trip reveals another issue; cpu_base.online is not set to 1 after the transition, which appears as a WARN_ON_ONCE in enqueue_hrtimer(). Aside of that, the bulk of the per CPU state is not reset either, which means there are dangling pointers in the worst case. Address this by adding a corresponding startup() callback, which resets the stale per CPU state and sets the online flag. [ tglx: Make the new callback unconditionally available, remove the online modification in the prepare() callback and clear the remaining state in the starting callback instead of the prepare callback ]

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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.

02

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 → Use After Free → 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-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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:H/I:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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-416
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0362Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service-Zustand oder andere nicht spezifizierte Effekte zu erzeugen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250219Security Bulletin 19 Feb 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Feb 2025, published on 19 February 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250213Security Bulletin 13 February 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 13 February 2025, published on 13 February 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1073Multiples vulnérabilités dans le noyau Linux de SUSE

ord?id=CVE-2023-53727 Référence CVE CVE-2023-53728 https://www.cve.org/CVERecord?id=CVE-2023-53728 Référence CVE CVE-2023-53729 https://www.cve.org/CVERecord?id=CVE-2023-53729 Référence CVE CVE-2023-53730 https://www.cve.org/CVERecord?id=CVE-2023-53730 Référence CVE CVE-2023-53731 https://www.cve.org/CVERecord?id=CVE-2023-53731 Référence CVE CVE-2023-53733 https://www.cve.org/CVERecord?id=CVE-2023-53733 Référence CVE CVE-2023-7324 https://www.cve.org/CVERecord?id=CVE-2023-7324 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-57891 https://www.cve.org/CVERecord?id=CVE-2024-57891 Référence CVE CVE-2024-57951 https://www.cve.org/CVERecord?id=CVE-2024-57951 Référence CVE CVE-2024-57952 https://www.cve.org/CVERecord?id=CVE-2024-57952 Référence CVE CVE-2024-58090 https://www.cve.org/CVERecord?id=CVE-2024-58090 Référence CVE CVE-2025-21816 https://www.cve.org/CVERecord?id=CVE-2025-21816 Référence CVE CVE-2025-22034 https://www.cve.org/CVERecord?id=CVE-2025-22034 Référence CVE CVE-2025-22077 https://www.cve.org/CVERecord?id=CVE-2025-22077 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=CVE-2025-23145 Référence CVE CVE-2025-37798 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

rd?id=CVE-2024-5642 Référence CVE CVE-2024-56433 https://www.cve.org/CVERecord?id=CVE-2024-56433 Référence CVE CVE-2024-56826 https://www.cve.org/CVERecord?id=CVE-2024-56826 Référence CVE CVE-2024-56827 https://www.cve.org/CVERecord?id=CVE-2024-56827 Référence CVE CVE-2024-57834 https://www.cve.org/CVERecord?id=CVE-2024-57834 Référence CVE CVE-2024-57883 https://www.cve.org/CVERecord?id=CVE-2024-57883 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57949 https://www.cve.org/CVERecord?id=CVE-2024-57949 Référence CVE CVE-2024-57951 https://www.cve.org/CVERecord?id=CVE-2024-57951 Référence CVE CVE-2024-57952 https://www.cve.org/CVERecord?id=CVE-2024-57952 Référence CVE CVE-2024-57953 https://www.cve.org/CVERecord?id=CVE-2024-57953 Référence CVE CVE-2024-57970 https://www.cve.org/CVERecord?id=CVE-2024-57970 Référence CVE CVE-2024-57973 https://www.cve.org/CVERecord?id=CVE-2024-57973 Référence CVE CVE-2024-57974 https://www.cve.org/CVERecord?id=CVE-2024-57974 Référence CVE CVE-2024-57975 https://www.cve.org/CVERecord?id=CVE-2024-57975 Référence CVE CVE-2024-57977 https://www.cve.org/CVERecord?id=CVE-2024-57977 Référence CVE CVE-2024-57979 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56551 Référence CVE CVE-2024-56599 https://www.cve.org/CVERecord?id=CVE-2024-56599 Référence CVE CVE-2024-56608 https://www.cve.org/CVERecord?id=CVE-2024-56608 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56721 https://www.cve.org/CVERecord?id=CVE-2024-56721 Référence CVE CVE-2024-57834 https://www.cve.org/CVERecord?id=CVE-2024-57834 Référence CVE CVE-2024-57924 https://www.cve.org/CVERecord?id=CVE-2024-57924 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57949 https://www.cve.org/CVERecord?id=CVE-2024-57949 Référence CVE CVE-2024-57951 https://www.cve.org/CVERecord?id=CVE-2024-57951 Référence CVE CVE-2024-57952 https://www.cve.org/CVERecord?id=CVE-2024-57952 Référence CVE CVE-2024-57973 https://www.cve.org/CVERecord?id=CVE-2024-57973 Référence CVE CVE-2024-57977 https://www.cve.org/CVERecord?id=CVE-2024-57977 Référence CVE CVE-2024-57978 https://www.cve.org/CVERecord?id=CVE-2024-57978 Référence CVE CVE-2024-57979 https://www.cve.org/CVERecord?id=CVE-2024-57979 Référence CVE CVE-2024-57980 https://www.cve.org/CVERecord?id=CVE-2024-57980 Référence CVE CVE-2024-57981 https://www.cve.org/CVERecord?id=CVE-2024-57981 Référence CVE CVE-2024-57986 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=CVE-2024-57946 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57951 https://www.cve.org/CVERecord?id=CVE-2024-57951 Référence CVE CVE-2024-58087 https://www.cve.org/CVERecord?id=CVE-2024-58087 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Référence CVE CVE-2025-0927 https://www.cve.org/CVERecord?id=CVE-2025-0927 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=CVE-2025-21636 Référence CVE CVE-2025-21637 https://www.cve.org/CVERecord?id=CVE-2025-21637 Référence CVE CVE-2025-21638 https://www.cve.org/CVERecord?id=CVE-2025-21638 Référence CVE CVE-2025-21639 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=CVE-2024-57946 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57949 https://www.cve.org/CVERecord?id=CVE-2024-57949 Référence CVE CVE-2024-57950 https://www.cve.org/CVERecord?id=CVE-2024-57950 Référence CVE CVE-2024-57951 https://www.cve.org/CVERecord?id=CVE-2024-57951 Référence CVE CVE-2024-57952 https://www.cve.org/CVERecord?id=CVE-2024-57952 Référence CVE CVE-2024-58087 https://www.cve.org/CVERecord?id=CVE-2024-58087 Référence CVE CVE-2025-0927 https://www.cve.org/CVERecord?id=CVE-2025-0927 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=CVE-2025-21636 Référence CVE CVE-2025-21637 https://www.cve.org/CVERecord?id=CVE-2025-21637 Référence CVE CVE-2025-21638 https://www.cve.org/CVERecord?id=CVE-2025-21638 Référence CVE CVE-2025-21639 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=CVE-2024-57946 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57951 https://www.cve.org/CVERecord?id=CVE-2024-57951 Référence CVE CVE-2024-58087 https://www.cve.org/CVERecord?id=CVE-2024-58087 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=CVE-2025-21636 Référence CVE CVE-2025-21637 https://www.cve.org/CVERecord?id=CVE-2025-21637 Référence CVE CVE-2025-21638 https://www.cve.org/CVERecord?id=CVE-2025-21638 Référence CVE CVE-2025-21639 https://www.cve.org/CVERecord?id=CVE-2025-21639 Référence CVE CVE-2025-21640 https://www.cve.org/CVERecord?id=CVE-2025-21640 Référence CVE CVE-2025-21646 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57922 Référence CVE CVE-2024-57925 https://www.cve.org/CVERecord?id=CVE-2024-57925 Référence CVE CVE-2024-57929 https://www.cve.org/CVERecord?id=CVE-2024-57929 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=CVE-2024-57946 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57951 https://www.cve.org/CVERecord?id=CVE-2024-57951 Référence CVE CVE-2024-58087 https://www.cve.org/CVERecord?id=CVE-2024-58087 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Référence CVE CVE-2025-0927 https://www.cve.org/CVERecord?id=CVE-2025-0927 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=CVE-2025-21636 Référence CVE CVE-2025-21637 https://www.cve.org/CVERecord?id=CVE-2025-21637 Référence CVE CVE-2025-21638 https://www.cve.org/CVERecord?id=CVE-2025-21638 Référence CVE CVE-2025-21639 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2024-57929 Référence CVE CVE-2024-57930 https://www.cve.org/CVERecord?id=CVE-2024-57930 Référence CVE CVE-2024-57931 https://www.cve.org/CVERecord?id=CVE-2024-57931 Référence CVE CVE-2024-57938 https://www.cve.org/CVERecord?id=CVE-2024-57938 Référence CVE CVE-2024-57939 https://www.cve.org/CVERecord?id=CVE-2024-57939 Référence CVE CVE-2024-57940 https://www.cve.org/CVERecord?id=CVE-2024-57940 Référence CVE CVE-2024-57946 https://www.cve.org/CVERecord?id=CVE-2024-57946 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57949 https://www.cve.org/CVERecord?id=CVE-2024-57949 Référence CVE CVE-2024-57951 https://www.cve.org/CVERecord?id=CVE-2024-57951 Référence CVE CVE-2025-21629 https://www.cve.org/CVERecord?id=CVE-2025-21629 Référence CVE CVE-2025-21631 https://www.cve.org/CVERecord?id=CVE-2025-21631 Référence CVE CVE-2025-21636 https://www.cve.org/CVERecord?id=CVE-2025-21636 Référence CVE CVE-2025-21637 https://www.cve.org/CVERecord?id=CVE-2025-21637 Référence CVE CVE-2025-21638 https://www.cve.org/CVERecord?id=CVE-2025-21638 Référence CVE CVE-2025-21639 https://www.cve.org/CVERecord?id=CVE-2025-21639 Référence CVE CVE-2025-21640 https://www.cve.org/CVERecord?id=CVE-2025-21640 Référence CVE CVE-2025-21646 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-019050Linux の Linux Kernel における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel には、解放済みメモリの使用に関する脆弱性が存在します。

Official advisory ↗
03

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 S7-1500 TM MFP - GNU/Linux subsystem
Fixed
Linux: < 6.7, 5.4.290 ≤ 5.4.*, 5.10.234 ≤ 5.10.*, 5.15.177 ≤ 5.15.*, 6.1.127 ≤ 6.1.*, 6.6.74 ≤ 6.6.*, 6.12.11 ≤ 6.12.*, 6.13 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 12 Feb 2025 · Last source change 23 May 2026, 15:56 UTC · CWE-416 · Use After Free

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-2024-53854
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
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.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-53854↗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.
Free version - for non-commercial use only.CVE-2024-57951 · cve.blacktree.nl