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

netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 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: No default targetRemediation target: Normal maintenance

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.3-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.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.3-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.

1 current
CVE-2024-56755 · CSAF 2.0 · revision 75 · interimSUSE Product Security TeamCVE-2024-56755
79 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • kernel-devel-azure as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING In fscache_create_volume(), there is a missing memory barrier between the bit-clearing operation and the wake-up operation. This may cause a situation where, after a wake-up, the bit-clearing operation hasn't been detected yet, leading to an indefinite wait. The triggering process is as follows: [cookie1] [cookie2] [volume_work] fscache_perform_lookup fscache_create_volume fscache_perform_lookup fscache_create_volume fscache_create_volume_work cachefiles_acquire_volume clear_and_wake_up_bit test_and_set_bit test_and_set_bit goto maybe_wait goto no_wait In the above process, cookie1 and cookie2 has the same volume. When cookie1 enters the -no_wait- process, it will clear the bit and wake up the waiting process. If a barrier is missing, it may cause cookie2 to remain in the -wait- process indefinitely. In commit 3288666c7256 ("fscache: Use clear_and_wake_up_bit() in fscache_create_volume_work()"), barriers were added to similar operations in fscache_create_volume_work(), but fscache_create_volume() was missed. By combining the clear and wake operations into clear_and_wake_up_bit() to fix this issue.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-53398

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. 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: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING In fscache_create_volume(), there is a missing memory barrier between the bit-clearing operation and the wake-up operation. This may cause a situation where, after a wake-up, the bit-clearing operation hasn't been detected yet, leading to an indefinite wait. The triggering process is as follows: [cookie1] [cookie2] [volume_work] fscache_perform_lookup fscache_create_volume fscache_perform_lookup fscache_create_volume fscache_create_volume_work cachefiles_acquire_volume clear_and_wake_up_bit test_and_set_bit test_and_set_bit goto maybe_wait goto no_wait In the above process, cookie1 and cookie2 has the same volume. When cookie1 enters the -no_wait- process, it will clear the bit and wake up the waiting process. If a barrier is missing, it may cause cookie2 to remain in the -wait- process indefinitely. In commit 3288666c7256 ("fscache: Use clear_and_wake_up_bit() in fscache_create_volume_work()"), barriers were added to similar operations in fscache_create_volume_work(), but fscache_create_volume() was missed. By combining the clear and wake operations into clear_and_wake_up_bit() to fix this issue.

What

In the Linux kernel, the following vulnerability has been resolved: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING In fscache_create_volume(), there is a missing memory barrier between the bit-clearing operation and the wake-up operation. This may cause a situation where, after a wake-up, the bit-clearing operation hasn't been detected yet, leading to an indefinite wait. The triggering process is as follows: [cookie1] [cookie2] [volume_work] fscache_perform_lookup fscache_create_volume fscache_perform_lookup fscache_create_volume fscache_create_volume_work cachefiles_acquire_volume clear_and_wake_up_bit test_and_set_bit test_and_set_bit goto maybe_wait goto no_wait In the above process, cookie1 and cookie2 has the same volume. When cookie1 enters the -no_wait- process, it will clear the bit and wake up the waiting process. If a barrier is missing, it may cause cookie2 to remain in the -wait- process indefinitely. In commit 3288666c7256 ("fscache: Use clear_and_wake_up_bit() in fscache_create_volume_work()"), barriers were added to similar operations in fscache_create_volume_work(), but fscache_create_volume() was missed. By combining the clear and wake operations into clear_and_wake_up_bit() to fix this issue.

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

In the Linux kernel, the following vulnerability has been resolved: netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING In fscache_create_volume(), there is a missing memory barrier between the bit-clearing operation and the wake-up operation. This may cause a situation where, after a wake-up, the bit-clearing operation hasn't been detected yet, leading to an indefinite wait. The triggering process is as follows: [cookie1] [cookie2] [volume_work] fscache_perform_lookup fscache_create_volume fscache_perform_lookup fscache_create_volume fscache_create_volume_work cachefiles_acquire_volume clear_and_wake_up_bit test_and_set_bit test_and_set_bit goto maybe_wait goto no_wait In the above process, cookie1 and cookie2 has the same volume. When cookie1 enters the -no_wait- process, it will clear the bit and wake up the waiting process. If a barrier is missing, it may cause cookie2 to remain in the -wait- process indefinitely. In commit 3288666c7256 ("fscache: Use clear_and_wake_up_bit() in fscache_create_volume_work()"), barriers were added to similar operations in fscache_create_volume_work(), but fscache_create_volume() was missed. By combining the clear and wake operations into clear_and_wake_up_bit() to fix this issue.

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.

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 → 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
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-3762Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.

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

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

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

d?id=CVE-2024-56742 Référence CVE CVE-2024-56744 https://www.cve.org/CVERecord?id=CVE-2024-56744 Référence CVE CVE-2024-56745 https://www.cve.org/CVERecord?id=CVE-2024-56745 Référence CVE CVE-2024-56746 https://www.cve.org/CVERecord?id=CVE-2024-56746 Référence CVE CVE-2024-56747 https://www.cve.org/CVERecord?id=CVE-2024-56747 Référence CVE CVE-2024-56748 https://www.cve.org/CVERecord?id=CVE-2024-56748 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56752 https://www.cve.org/CVERecord?id=CVE-2024-56752 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-56763 https://www.cve.org/CVERecord?id=CVE-2024-56763 Référence CVE CVE-2024-56765 https://www.cve.org/CVERecord?id=CVE-2024-56765 Référence CVE CVE-2024-56767 https://www.cve.org/CVERecord?id=CVE-2024-56767 Référence CVE CVE-2024-56769 https://www.cve.org/CVERecord?id=CVE-2024-56769 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-56771 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-56742 Référence CVE CVE-2024-56744 https://www.cve.org/CVERecord?id=CVE-2024-56744 Référence CVE CVE-2024-56745 https://www.cve.org/CVERecord?id=CVE-2024-56745 Référence CVE CVE-2024-56746 https://www.cve.org/CVERecord?id=CVE-2024-56746 Référence CVE CVE-2024-56747 https://www.cve.org/CVERecord?id=CVE-2024-56747 Référence CVE CVE-2024-56748 https://www.cve.org/CVERecord?id=CVE-2024-56748 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56752 https://www.cve.org/CVERecord?id=CVE-2024-56752 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-56763 https://www.cve.org/CVERecord?id=CVE-2024-56763 Référence CVE CVE-2024-56765 https://www.cve.org/CVERecord?id=CVE-2024-56765 Référence CVE CVE-2024-56767 https://www.cve.org/CVERecord?id=CVE-2024-56767 Référence CVE CVE-2024-56769 https://www.cve.org/CVERecord?id=CVE-2024-56769 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=CVE-2024-56770 Référence CVE CVE-2024-56771 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-56698 Référence CVE CVE-2024-56701 https://www.cve.org/CVERecord?id=CVE-2024-56701 Référence CVE CVE-2024-56704 https://www.cve.org/CVERecord?id=CVE-2024-56704 Référence CVE CVE-2024-56720 https://www.cve.org/CVERecord?id=CVE-2024-56720 Référence CVE CVE-2024-56722 https://www.cve.org/CVERecord?id=CVE-2024-56722 Référence CVE CVE-2024-56739 https://www.cve.org/CVERecord?id=CVE-2024-56739 Référence CVE CVE-2024-56745 https://www.cve.org/CVERecord?id=CVE-2024-56745 Référence CVE CVE-2024-56747 https://www.cve.org/CVERecord?id=CVE-2024-56747 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?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=

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

d?id=CVE-2024-56728 Référence CVE CVE-2024-56739 https://www.cve.org/CVERecord?id=CVE-2024-56739 Référence CVE CVE-2024-56741 https://www.cve.org/CVERecord?id=CVE-2024-56741 Référence CVE CVE-2024-56745 https://www.cve.org/CVERecord?id=CVE-2024-56745 Référence CVE CVE-2024-56746 https://www.cve.org/CVERecord?id=CVE-2024-56746 Référence CVE CVE-2024-56747 https://www.cve.org/CVERecord?id=CVE-2024-56747 Référence CVE CVE-2024-56748 https://www.cve.org/CVERecord?id=CVE-2024-56748 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-56763 https://www.cve.org/CVERecord?id=CVE-2024-56763 Référence CVE CVE-2024-56765 https://www.cve.org/CVERecord?id=CVE-2024-56765 Référence CVE CVE-2024-56766 https://www.cve.org/CVERecord?id=CVE-2024-56766 Référence CVE CVE-2024-56767 https://www.cve.org/CVERecord?id=CVE-2024-56767 Référence CVE CVE-2024-56769 https://www.cve.org/CVERecord?id=CVE-2024-56769 Référence CVE CVE-2024-56770 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56744 Référence CVE CVE-2024-56745 https://www.cve.org/CVERecord?id=CVE-2024-56745 Référence CVE CVE-2024-56746 https://www.cve.org/CVERecord?id=CVE-2024-56746 Référence CVE CVE-2024-56747 https://www.cve.org/CVERecord?id=CVE-2024-56747 Référence CVE CVE-2024-56748 https://www.cve.org/CVERecord?id=CVE-2024-56748 Référence CVE CVE-2024-56749 https://www.cve.org/CVERecord?id=CVE-2024-56749 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56752 https://www.cve.org/CVERecord?id=CVE-2024-56752 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2025-0927 https://www.cve.org/CVERecord?id=CVE-2025-0927 Gestion détaillée du document le 07 mars 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2024-56744 Référence CVE CVE-2024-56745 https://www.cve.org/CVERecord?id=CVE-2024-56745 Référence CVE CVE-2024-56746 https://www.cve.org/CVERecord?id=CVE-2024-56746 Référence CVE CVE-2024-56747 https://www.cve.org/CVERecord?id=CVE-2024-56747 Référence CVE CVE-2024-56748 https://www.cve.org/CVERecord?id=CVE-2024-56748 Référence CVE CVE-2024-56749 https://www.cve.org/CVERecord?id=CVE-2024-56749 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-56752 https://www.cve.org/CVERecord?id=CVE-2024-56752 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2025-0927 https://www.cve.org/CVERecord?id=CVE-2025-0927 Gestion détaillée du document le 21 février 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2024-56729 Référence CVE CVE-2024-56739 https://www.cve.org/CVERecord?id=CVE-2024-56739 Référence CVE CVE-2024-56741 https://www.cve.org/CVERecord?id=CVE-2024-56741 Référence CVE CVE-2024-56745 https://www.cve.org/CVERecord?id=CVE-2024-56745 Référence CVE CVE-2024-56746 https://www.cve.org/CVERecord?id=CVE-2024-56746 Référence CVE CVE-2024-56747 https://www.cve.org/CVERecord?id=CVE-2024-56747 Référence CVE CVE-2024-56748 https://www.cve.org/CVERecord?id=CVE-2024-56748 Référence CVE CVE-2024-56752 https://www.cve.org/CVERecord?id=CVE-2024-56752 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-56759 https://www.cve.org/CVERecord?id=CVE-2024-56759 Référence CVE CVE-2024-56760 https://www.cve.org/CVERecord?id=CVE-2024-56760 Référence CVE CVE-2024-56765 https://www.cve.org/CVERecord?id=CVE-2024-56765 Référence CVE CVE-2024-56766 https://www.cve.org/CVERecord?id=CVE-2024-56766 Référence CVE CVE-2024-56767 https://www.cve.org/CVERecord?id=CVE-2024-56767 Référence CVE CVE-2024-56769 https://www.cve.org/CVERecord?id=CVE-2024-56769 Référence CVE CVE-2024-56774 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56619 https://www.cve.org/CVERecord?id=CVE-2024-56619 Référence CVE CVE-2024-56631 https://www.cve.org/CVERecord?id=CVE-2024-56631 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56667 https://www.cve.org/CVERecord?id=CVE-2024-56667 Référence CVE CVE-2024-56704 https://www.cve.org/CVERecord?id=CVE-2024-56704 Référence CVE CVE-2024-56752 https://www.cve.org/CVERecord?id=CVE-2024-56752 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Gestion détaillée du document le 24 janvier 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2024-56576 Référence CVE CVE-2024-56582 https://www.cve.org/CVERecord?id=CVE-2024-56582 Référence CVE CVE-2024-56599 https://www.cve.org/CVERecord?id=CVE-2024-56599 Référence CVE CVE-2024-56604 https://www.cve.org/CVERecord?id=CVE-2024-56604 Référence CVE CVE-2024-56605 https://www.cve.org/CVERecord?id=CVE-2024-56605 Référence CVE CVE-2024-56645 https://www.cve.org/CVERecord?id=CVE-2024-56645 Référence CVE CVE-2024-56667 https://www.cve.org/CVERecord?id=CVE-2024-56667 Référence CVE CVE-2024-56752 https://www.cve.org/CVERecord?id=CVE-2024-56752 Référence CVE CVE-2024-56754 https://www.cve.org/CVERecord?id=CVE-2024-56754 Référence CVE CVE-2024-56755 https://www.cve.org/CVERecord?id=CVE-2024-56755 Référence CVE CVE-2024-56756 https://www.cve.org/CVERecord?id=CVE-2024-56756 Référence CVE CVE-2024-8805 https://www.cve.org/CVERecord?id=CVE-2024-8805 Gestion détaillée du document le 17 janvier 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-015798Linux の 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: < 5.17, 6.1.120 ≤ 6.1.*, 6.6.64 ≤ 6.6.*, 6.11.11 ≤ 6.11.*, 6.12.2 ≤ 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 29 Dec 2024 · Last source change 11 May 2026, 20:58 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-2024-53398
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-53398↗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-56755 · cve.blacktree.nl