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

s390/cpum_sf: Handle CPU hotplug remove during sampling

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.21% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

23 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 19 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.123-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.5-1Debian Security Tracker ↗Source updated 6 Oct 2026
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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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
CVE-2024-57849 · CSAF 2.0 · revision 91 · interimSUSE Product Security TeamCVE-2024-57849
181 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: s390/cpum_sf: Handle CPU hotplug remove during sampling CPU hotplug remove handling triggers the following function call sequence: CPUHP_AP_PERF_S390_SF_ONLINE --> s390_pmu_sf_offline_cpu() ... CPUHP_AP_PERF_ONLINE --> perf_event_exit_cpu() The s390 CPUMF sampling CPU hotplug handler invokes: s390_pmu_sf_offline_cpu() +--> cpusf_pmu_setup() +--> setup_pmc_cpu() +--> deallocate_buffers() This function de-allocates all sampling data buffers (SDBs) allocated for that CPU at event initialization. It also clears the PMU_F_RESERVED bit. The CPU is gone and can not be sampled. With the event still being active on the removed CPU, the CPU event hotplug support in kernel performance subsystem triggers the following function calls on the removed CPU: perf_event_exit_cpu() +--> perf_event_exit_cpu_context() +--> __perf_event_exit_context() +--> __perf_remove_from_context() +--> event_sched_out() +--> cpumsf_pmu_del() +--> cpumsf_pmu_stop() +--> hw_perf_event_update() to stop and remove the event. During removal of the event, the sampling device driver tries to read out the remaining samples from the sample data buffers (SDBs). But they have already been freed (and may have been re-assigned). This may lead to a use after free situation in which case the samples are most likely invalid. In the best case the memory has not been reassigned and still contains valid data. Remedy this situation and check if the CPU is still in reserved state (bit PMU_F_RESERVED set). In this case the SDBs have not been released an contain valid data. This is always the case when the event is removed (and no CPU hotplug off occured). If the PMU_F_RESERVED bit is not set, the SDB buffers are gone.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2024-57849 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: s390/cpum_sf: Handle CPU hotplug remove during sampling
136 known affected

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

  • bpftool as a component of Red Hat Enterprise Linux 7
  • kernel as a component of Red Hat Enterprise Linux 7
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 7
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 7
  • kernel-debug as a component of Red Hat Enterprise Linux 7
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 7
  • kernel-devel as a component of Red Hat Enterprise Linux 7
  • kernel-doc as a component of Red Hat Enterprise Linux 7
  • kernel-headers as a component of Red Hat Enterprise Linux 7
  • kernel-kdump as a component of Red Hat Enterprise Linux 7
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 7
  • kernel-rt as a component of Red Hat Enterprise Linux 7
Summary
A vulnerability was found in the Linux Kernel. This issue affects performance monitoring on the `s390` architecture during specific CPU hotplug scenarios.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-53773

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 actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: s390/cpum_sf: Handle CPU hotplug remove during sampling CPU hotplug remove handling triggers the following function call sequence: CPUHP_AP_PERF_S390_SF_ONLINE --> s390_pmu_sf_offline_cpu() ... CPUHP_AP_PERF_ONLINE --> perf_event_exit_cpu() The s390 CPUMF sampling CPU hotplug handler invokes: s390_pmu_sf_offline_cpu() +--> cpusf_pmu_setup() +--> setup_pmc_cpu() +--> deallocate_buffers() This function de-allocates all sampling data buffers (SDBs) allocated for that CPU at event initialization. It also clears the PMU_F_RESERVED bit. The CPU is gone and can not be sampled. With the event still being active on the removed CPU, the CPU event hotplug support in kernel performance subsystem triggers the following function calls on the removed CPU: perf_event_exit_cpu() +--> perf_event_exit_cpu_context() +--> __perf_event_exit_context() +--> __perf_remove_from_context() +--> event_sched_out() +--> cpumsf_pmu_del() +--> cpumsf_pmu_stop() +--> hw_perf_event_update() to stop and remove the event. During removal of the event, the sampling device driver tries to read out the remaining samples from the sample data buffers (SDBs). But they have already been freed (and may have been re-assigned). This may lead to a use after free situation in which case the samples are most likely invalid. In the best case the memory has not been reassigned and still contains valid data. Remedy this situation and check if the CPU is still in reserved state (bit PMU_F_RESERVED set). In this case the SDBs have not been released an contain valid data. This is always the case when the event is removed (and no CPU hotplug off occured). If the PMU_F_RESERVED bit is not set, the SDB buffers are gone.

What

In the Linux kernel, the following vulnerability has been resolved: s390/cpum_sf: Handle CPU hotplug remove during sampling CPU hotplug remove handling triggers the following function call sequence: CPUHP_AP_PERF_S390_SF_ONLINE --> s390_pmu_sf_offline_cpu() ... CPUHP_AP_PERF_ONLINE --> perf_event_exit_cpu() The s390 CPUMF sampling CPU hotplug handler invokes: s390_pmu_sf_offline_cpu() +--> cpusf_pmu_setup() +--> setup_pmc_cpu() +--> deallocate_buffers() This function de-allocates all sampling data buffers (SDBs) allocated for that CPU at event initialization. It also clears the PMU_F_RESERVED bit. The CPU is gone and can not be sampled. With the event still being active on the removed CPU, the CPU event hotplug support in kernel performance subsystem triggers the following function calls on the removed CPU: perf_event_exit_cpu() +--> perf_event_exit_cpu_context() +--> __perf_event_exit_context() +--> __perf_remove_from_context() +--> event_sched_out() +--> cpumsf_pmu_del() +--> cpumsf_pmu_stop() +--> hw_perf_event_update() to stop and remove the event. During removal of the event, the sampling device driver tries to read out the remaining samples from the sample data buffers (SDBs). But they have already been freed (and may have been re-assigned). This may lead to a use after free situation in which case the samples are most likely invalid. In the best case the memory has not been reassigned and still contains valid data. Remedy this situation and check if the CPU is still in reserved state (bit PMU_F_RESERVED set). In this case the SDBs have not been released an contain valid data. This is always the case when the event is removed (and no CPU hotplug off occured). If the PMU_F_RESERVED bit is not set, the SDB buffers are gone.

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: s390/cpum_sf: Handle CPU hotplug remove during sampling CPU hotplug remove handling triggers the following function call sequence: CPUHP_AP_PERF_S390_SF_ONLINE --> s390_pmu_sf_offline_cpu() ... CPUHP_AP_PERF_ONLINE --> perf_event_exit_cpu() The s390 CPUMF sampling CPU hotplug handler invokes: s390_pmu_sf_offline_cpu() +--> cpusf_pmu_setup() +--> setup_pmc_cpu() +--> deallocate_buffers() This function de-allocates all sampling data buffers (SDBs) allocated for that CPU at event initialization. It also clears the PMU_F_RESERVED bit. The CPU is gone and can not be sampled. With the event still being active on the removed CPU, the CPU event hotplug support in kernel performance subsystem triggers the following function calls on the removed CPU: perf_event_exit_cpu() +--> perf_event_exit_cpu_context() +--> __perf_event_exit_context() +--> __perf_remove_from_context() +--> event_sched_out() +--> cpumsf_pmu_del() +--> cpumsf_pmu_stop() +--> hw_perf_event_update() to stop and remove the event. During removal of the event, the sampling device driver tries to read out the remaining samples from the sample data buffers (SDBs). But they have already been freed (and may have been re-assigned). This may lead to a use after free situation in which case the samples are most likely invalid. In the best case the memory has not been reassigned and still contains valid data. Remedy this situation and check if the CPU is still in reserved state (bit PMU_F_RESERVED set). In this case the SDBs have not been released an contain valid data. This is always the case when the event is removed (and no CPU hotplug off occured). If the PMU_F_RESERVED bit is not set, the SDB buffers are gone.

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-2026-3595IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2025-0047Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen und weitere nicht spezifizierte Angriffe zu starten.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250115Security Bulletin 15 Jan 2025

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

lletin de sécurité IBM 7290182 du 30 septembre 2026 https://www.ibm.com/support/pages/node/7290182 Référence CVE CVE-2018-16487 https://www.cve.org/CVERecord?id=CVE-2018-16487 Référence CVE CVE-2020-15366 https://www.cve.org/CVERecord?id=CVE-2020-15366 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2022-24999 https://www.cve.org/CVERecord?id=CVE-2022-24999 Référence CVE CVE-2022-3517 https://www.cve.org/CVERecord?id=CVE-2022-3517 Référence CVE CVE-2024-55565 https://www.cve.org/CVERecord?id=CVE-2024-55565 Référence CVE CVE-2024-56602 https://www.cve.org/CVERecord?id=CVE-2024-56602 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2025-13465 https://www.cve.org/CVERecord?id=CVE-2025-13465 Référence CVE CVE-2025-14813 https://www.cve.org/CVERecord?id=CVE-2025-14813 Référence CVE CVE-2025-15284 https://www.cve.org/CVERecord?id=CVE-2025-15284 Référence CVE CVE-2025-27152 https://www.cve.org/CVERecord?id=CVE-2025-27152 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-39902 https://www.cve.org/CVERecord?id=CVE-2025-39902 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-46653 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1118Multiples vulnérabilités dans le noyau Linux de Red Hat

rrata/RHSA-2026:63013 Bulletin de sécurité Red Hat RHSA-2026:63014 du 03 septembre 2026 https://access.redhat.com/errata/RHSA-2026:63014 Bulletin de sécurité Red Hat RHSA-2026:63189 du 03 septembre 2026 https://access.redhat.com/errata/RHSA-2026:63189 Bulletin de sécurité Red Hat RHSA-2026:63537 du 04 septembre 2026 https://access.redhat.com/errata/RHSA-2026:63537 Bulletin de sécurité Red Hat RHSA-2026:63539 du 04 septembre 2026 https://access.redhat.com/errata/RHSA-2026:63539 Référence CVE CVE-2023-52924 https://www.cve.org/CVERecord?id=CVE-2023-52924 Référence CVE CVE-2024-46744 https://www.cve.org/CVERecord?id=CVE-2024-46744 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2025-21834 https://www.cve.org/CVERecord?id=CVE-2025-21834 Référence CVE CVE-2025-68211 https://www.cve.org/CVERecord?id=CVE-2025-68211 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2026-23003 https://www.cve.org/CVERecord?id=CVE-2026-23003 Référence CVE CVE-2026-43023 https://www.cve.org/CVERecord?id=CVE-2026-43023 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43450 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-54322 Référence CVE CVE-2023-54324 https://www.cve.org/CVERecord?id=CVE-2023-54324 Référence CVE CVE-2023-54325 https://www.cve.org/CVERecord?id=CVE-2023-54325 Référence CVE CVE-2023-54326 https://www.cve.org/CVERecord?id=CVE-2023-54326 Référence CVE CVE-2024-26944 https://www.cve.org/CVERecord?id=CVE-2024-26944 Référence CVE CVE-2024-36933 https://www.cve.org/CVERecord?id=CVE-2024-36933 Référence CVE CVE-2024-53093 https://www.cve.org/CVERecord?id=CVE-2024-53093 Référence CVE CVE-2024-53164 https://www.cve.org/CVERecord?id=CVE-2024-53164 Référence CVE CVE-2024-56590 https://www.cve.org/CVERecord?id=CVE-2024-56590 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2025-38085 https://www.cve.org/CVERecord?id=CVE-2025-38085 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38336 https://www.cve.org/CVERecord?id=CVE-2025-38336 Référence CVE CVE-2025-38476 https://www.cve.org/CVERecord?id=CVE-2025-38476 Référence CVE CVE-2025-38500 https://www.cve.org/CVERecord?id=CVE-2025-38500 Référence CVE CVE-2025-38554 https://www.cve.org/CVERecord?id=CVE-2025-38554 Référence CVE CVE-2025-38572 https://www.cve.org/CVERecord?id=CVE-2025-38572 Référence CVE CVE-2025-38588 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-36978 Référence CVE CVE-2024-46800 https://www.cve.org/CVERecord?id=CVE-2024-46800 Référence CVE CVE-2024-53057 https://www.cve.org/CVERecord?id=CVE-2024-53057 Référence CVE CVE-2024-53125 https://www.cve.org/CVERecord?id=CVE-2024-53125 Référence CVE CVE-2024-53141 https://www.cve.org/CVERecord?id=CVE-2024-53141 Référence CVE CVE-2024-53168 https://www.cve.org/CVERecord?id=CVE-2024-53168 Référence CVE CVE-2024-53177 https://www.cve.org/CVERecord?id=CVE-2024-53177 Référence CVE CVE-2024-56558 https://www.cve.org/CVERecord?id=CVE-2024-56558 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57947 https://www.cve.org/CVERecord?id=CVE-2024-57947 Référence CVE CVE-2024-57999 https://www.cve.org/CVERecord?id=CVE-2024-57999 Référence CVE CVE-2024-58239 https://www.cve.org/CVERecord?id=CVE-2024-58239 Référence CVE CVE-2025-21700 https://www.cve.org/CVERecord?id=CVE-2025-21700 Référence CVE CVE-2025-21702 https://www.cve.org/CVERecord?id=CVE-2025-21702 Référence CVE CVE-2025-21703 https://www.cve.org/CVERecord?id=CVE-2025-21703 Référence CVE CVE-2025-21756 https://www.cve.org/CVERecord?id=CVE-2025-21756 Référence CVE CVE-2025-21888 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-56787 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57792 https://www.cve.org/CVERecord?id=CVE-2024-57792 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57802 https://www.cve.org/CVERecord?id=CVE-2024-57802 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57841 https://www.cve.org/CVERecord?id=CVE-2024-57841 Référence CVE CVE-2024-57843 https://www.cve.org/CVERecord?id=CVE-2024-57843 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57872 https://www.cve.org/CVERecord?id=CVE-2024-57872 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56787 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57792 https://www.cve.org/CVERecord?id=CVE-2024-57792 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57802 https://www.cve.org/CVERecord?id=CVE-2024-57802 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57841 https://www.cve.org/CVERecord?id=CVE-2024-57841 Référence CVE CVE-2024-57843 https://www.cve.org/CVERecord?id=CVE-2024-57843 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57872 https://www.cve.org/CVERecord?id=CVE-2024-57872 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56785 Référence CVE CVE-2024-56787 https://www.cve.org/CVERecord?id=CVE-2024-56787 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57792 https://www.cve.org/CVERecord?id=CVE-2024-57792 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57802 https://www.cve.org/CVERecord?id=CVE-2024-57802 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57841 https://www.cve.org/CVERecord?id=CVE-2024-57841 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57896 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-56785 Référence CVE CVE-2024-56787 https://www.cve.org/CVERecord?id=CVE-2024-56787 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57792 https://www.cve.org/CVERecord?id=CVE-2024-57792 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57802 https://www.cve.org/CVERecord?id=CVE-2024-57802 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57841 https://www.cve.org/CVERecord?id=CVE-2024-57841 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=CVE-2024-57892 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57804 Référence CVE CVE-2024-57805 https://www.cve.org/CVERecord?id=CVE-2024-57805 Référence CVE CVE-2024-57806 https://www.cve.org/CVERecord?id=CVE-2024-57806 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57809 https://www.cve.org/CVERecord?id=CVE-2024-57809 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57839 https://www.cve.org/CVERecord?id=CVE-2024-57839 Référence CVE CVE-2024-57841 https://www.cve.org/CVERecord?id=CVE-2024-57841 Référence CVE CVE-2024-57843 https://www.cve.org/CVERecord?id=CVE-2024-57843 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57857 https://www.cve.org/CVERecord?id=CVE-2024-57857 Référence CVE CVE-2024-57872 https://www.cve.org/CVERecord?id=CVE-2024-57872 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57875 https://www.cve.org/CVERecord?id=CVE-2024-57875 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57878 https://www.cve.org/CVERecord?id=CVE-2024-57878 Référence CVE CVE-2024-57879 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56647 Référence CVE CVE-2024-56648 https://www.cve.org/CVERecord?id=CVE-2024-56648 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56720 https://www.cve.org/CVERecord?id=CVE-2024-56720 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 Référence CVE CVE-2024-57994 https://www.cve.org/CVERecord?id=CVE-2024-57994 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=

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

d?id=CVE-2024-56759 Référence CVE CVE-2024-56765 https://www.cve.org/CVERecord?id=CVE-2024-56765 Référence CVE CVE-2024-56776 https://www.cve.org/CVERecord?id=CVE-2024-56776 Référence CVE CVE-2024-56777 https://www.cve.org/CVERecord?id=CVE-2024-56777 Référence CVE CVE-2024-56778 https://www.cve.org/CVERecord?id=CVE-2024-56778 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57792 https://www.cve.org/CVERecord?id=CVE-2024-57792 Référence CVE CVE-2024-57793 https://www.cve.org/CVERecord?id=CVE-2024-57793 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57896 https://www.cve.org/CVERecord?id=CVE-2024-57896 Référence CVE CVE-2024-57897 https://www.cve.org/CVERecord?id=CVE-2024-57897 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56785 Référence CVE CVE-2024-56787 https://www.cve.org/CVERecord?id=CVE-2024-56787 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57792 https://www.cve.org/CVERecord?id=CVE-2024-57792 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57802 https://www.cve.org/CVERecord?id=CVE-2024-57802 Référence CVE CVE-2024-57807 https://www.cve.org/CVERecord?id=CVE-2024-57807 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57841 https://www.cve.org/CVERecord?id=CVE-2024-57841 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56623 Référence CVE CVE-2024-56647 https://www.cve.org/CVERecord?id=CVE-2024-56647 Référence CVE CVE-2024-56650 https://www.cve.org/CVERecord?id=CVE-2024-56650 Référence CVE CVE-2024-56658 https://www.cve.org/CVERecord?id=CVE-2024-56658 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56720 https://www.cve.org/CVERecord?id=CVE-2024-56720 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-57791 https://www.cve.org/CVERecord?id=CVE-2024-57791 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57889 https://www.cve.org/CVERecord?id=CVE-2024-57889 Référence CVE CVE-2024-57893 https://www.cve.org/CVERecord?id=CVE-2024-57893 Référence CVE CVE-2024-57948 https://www.cve.org/CVERecord?id=CVE-2024-57948 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=

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

d?id=CVE-2024-57792 Référence CVE CVE-2024-57793 https://www.cve.org/CVERecord?id=CVE-2024-57793 Référence CVE CVE-2024-57795 https://www.cve.org/CVERecord?id=CVE-2024-57795 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57801 https://www.cve.org/CVERecord?id=CVE-2024-57801 Référence CVE CVE-2024-57802 https://www.cve.org/CVERecord?id=CVE-2024-57802 Référence CVE CVE-2024-57804 https://www.cve.org/CVERecord?id=CVE-2024-57804 Référence CVE CVE-2024-57809 https://www.cve.org/CVERecord?id=CVE-2024-57809 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57857 https://www.cve.org/CVERecord?id=CVE-2024-57857 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57792 Référence CVE CVE-2024-57793 https://www.cve.org/CVERecord?id=CVE-2024-57793 Référence CVE CVE-2024-57795 https://www.cve.org/CVERecord?id=CVE-2024-57795 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57801 https://www.cve.org/CVERecord?id=CVE-2024-57801 Référence CVE CVE-2024-57802 https://www.cve.org/CVERecord?id=CVE-2024-57802 Référence CVE CVE-2024-57804 https://www.cve.org/CVERecord?id=CVE-2024-57804 Référence CVE CVE-2024-57809 https://www.cve.org/CVERecord?id=CVE-2024-57809 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57857 https://www.cve.org/CVERecord?id=CVE-2024-57857 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57882 https://www.cve.org/CVERecord?id=CVE-2024-57882 Référence CVE CVE-2024-57884 https://www.cve.org/CVERecord?id=CVE-2024-57884 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-57791 Référence CVE CVE-2024-57792 https://www.cve.org/CVERecord?id=CVE-2024-57792 Référence CVE CVE-2024-57793 https://www.cve.org/CVERecord?id=CVE-2024-57793 Référence CVE CVE-2024-57795 https://www.cve.org/CVERecord?id=CVE-2024-57795 Référence CVE CVE-2024-57798 https://www.cve.org/CVERecord?id=CVE-2024-57798 Référence CVE CVE-2024-57801 https://www.cve.org/CVERecord?id=CVE-2024-57801 Référence CVE CVE-2024-57804 https://www.cve.org/CVERecord?id=CVE-2024-57804 Référence CVE CVE-2024-57809 https://www.cve.org/CVERecord?id=CVE-2024-57809 Référence CVE CVE-2024-57838 https://www.cve.org/CVERecord?id=CVE-2024-57838 Référence CVE CVE-2024-57849 https://www.cve.org/CVERecord?id=CVE-2024-57849 Référence CVE CVE-2024-57850 https://www.cve.org/CVERecord?id=CVE-2024-57850 Référence CVE CVE-2024-57857 https://www.cve.org/CVERecord?id=CVE-2024-57857 Référence CVE CVE-2024-57874 https://www.cve.org/CVERecord?id=CVE-2024-57874 Référence CVE CVE-2024-57876 https://www.cve.org/CVERecord?id=CVE-2024-57876 Référence CVE CVE-2024-57887 https://www.cve.org/CVERecord?id=CVE-2024-57887 Référence CVE CVE-2024-57888 https://www.cve.org/CVERecord?id=CVE-2024-57888 Référence CVE CVE-2024-57890 https://www.cve.org/CVERecord?id=CVE-2024-57890 Référence CVE CVE-2024-57892 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028922Linux の 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.
Fix availability varies by product
Affected
Fixed
Linux: < 4.8, 5.4.287 ≤ 5.4.*, 5.10.231 ≤ 5.10.*, 5.15.174 ≤ 5.15.*, 6.1.120 ≤ 6.1.*, 6.6.66 ≤ 6.6.*, 6.12.5 ≤ 6.12.*, 6.13 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 11 Jan 2025 · Last source change 5 Aug 2026, 11:46 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-53773
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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.

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-53773↗Vendor CSAF · SUSE Product Security Team↗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-57849 · cve.blacktree.nl