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

cachefiles: fix dentry leak in cachefiles_open_file()

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 17 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.24% 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 17 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.

21 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 17 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.11.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.115-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.4-1Debian Security Tracker ↗Source updated 5 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-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-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-49870 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: cachefiles: fix dentry leak in cachefiles_open_file()
64 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's cachefiles component. A local attacker could exploit a dentry (directory entry) leak caused by a concurrency issue between a lookup cookie and a cull operation. This flaw prevents the proper release of a reference count, which can lead to resource exhaustion and a denial of service when the affected filesystem is unmounted.
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.
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-43716

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 17 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: cachefiles: fix dentry leak in cachefiles_open_file() A dentry leak may be caused when a lookup cookie and a cull are concurrent: P1 | P2 ----------------------------------------------------------- cachefiles_lookup_cookie cachefiles_look_up_object lookup_one_positive_unlocked // get dentry cachefiles_cull inode->i_flags |= S_KERNEL_FILE; cachefiles_open_file cachefiles_mark_inode_in_use __cachefiles_mark_inode_in_use can_use = false if (!(inode->i_flags & S_KERNEL_FILE)) can_use = true return false return false // Returns an error but doesn't put dentry After that the following WARNING will be triggered when the backend folder is umounted: ================================================================== BUG: Dentry 000000008ad87947{i=7a,n=Dx_1_1.img} still in use (1) [unmount of ext4 sda] WARNING: CPU: 4 PID: 359261 at fs/dcache.c:1767 umount_check+0x5d/0x70 CPU: 4 PID: 359261 Comm: umount Not tainted 6.6.0-dirty #25 RIP: 0010:umount_check+0x5d/0x70 Call Trace: <TASK> d_walk+0xda/0x2b0 do_one_tree+0x20/0x40 shrink_dcache_for_umount+0x2c/0x90 generic_shutdown_super+0x20/0x160 kill_block_super+0x1a/0x40 ext4_kill_sb+0x22/0x40 deactivate_locked_super+0x35/0x80 cleanup_mnt+0x104/0x160 ================================================================== Whether cachefiles_open_file() returns true or false, the reference count obtained by lookup_positive_unlocked() in cachefiles_look_up_object() should be released. Therefore release that reference count in cachefiles_look_up_object() to fix the above issue and simplify the code.

What

In the Linux kernel, the following vulnerability has been resolved: cachefiles: fix dentry leak in cachefiles_open_file() A dentry leak may be caused when a lookup cookie and a cull are concurrent: P1 | P2 ----------------------------------------------------------- cachefiles_lookup_cookie cachefiles_look_up_object lookup_one_positive_unlocked // get dentry cachefiles_cull inode->i_flags |= S_KERNEL_FILE; cachefiles_open_file cachefiles_mark_inode_in_use __cachefiles_mark_inode_in_use can_use = false if (!(inode->i_flags & S_KERNEL_FILE)) can_use = true return false return false // Returns an error but doesn't put dentry After that the following WARNING will be triggered when the backend folder is umounted: ================================================================== BUG: Dentry 000000008ad87947{i=7a,n=Dx_1_1.img} still in use (1) [unmount of ext4 sda] WARNING: CPU: 4 PID: 359261 at fs/dcache.c:1767 umount_check+0x5d/0x70 CPU: 4 PID: 359261 Comm: umount Not tainted 6.6.0-dirty #25 RIP: 0010:umount_check+0x5d/0x70 Call Trace: <TASK> d_walk+0xda/0x2b0 do_one_tree+0x20/0x40 shrink_dcache_for_umount+0x2c/0x90 generic_shutdown_super+0x20/0x160 kill_block_super+0x1a/0x40 ext4_kill_sb+0x22/0x40 deactivate_locked_super+0x35/0x80 cleanup_mnt+0x104/0x160 ================================================================== Whether cachefiles_open_file() returns true or false, the reference count obtained by lookup_positive_unlocked() in cachefiles_look_up_object() should be released. Therefore release that reference count in cachefiles_look_up_object() to fix the above issue and simplify the code.

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: cachefiles: fix dentry leak in cachefiles_open_file() A dentry leak may be caused when a lookup cookie and a cull are concurrent: P1 | P2 ----------------------------------------------------------- cachefiles_lookup_cookie cachefiles_look_up_object lookup_one_positive_unlocked // get dentry cachefiles_cull inode->i_flags |= S_KERNEL_FILE; cachefiles_open_file cachefiles_mark_inode_in_use __cachefiles_mark_inode_in_use can_use = false if (!(inode->i_flags & S_KERNEL_FILE)) can_use = true return false return false // Returns an error but doesn't put dentry After that the following WARNING will be triggered when the backend folder is umounted: ================================================================== BUG: Dentry 000000008ad87947{i=7a,n=Dx_1_1.img} still in use (1) [unmount of ext4 sda] WARNING: CPU: 4 PID: 359261 at fs/dcache.c:1767 umount_check+0x5d/0x70 CPU: 4 PID: 359261 Comm: umount Not tainted 6.6.0-dirty #25 RIP: 0010:umount_check+0x5d/0x70 Call Trace: <TASK> d_walk+0xda/0x2b0 do_one_tree+0x20/0x40 shrink_dcache_for_umount+0x2c/0x90 generic_shutdown_super+0x20/0x160 kill_block_super+0x1a/0x40 ext4_kill_sb+0x22/0x40 deactivate_locked_super+0x35/0x80 cleanup_mnt+0x104/0x160 ================================================================== Whether cachefiles_open_file() returns true or false, the reference count obtained by lookup_positive_unlocked() in cachefiles_look_up_object() should be released. Therefore release that reference count in cachefiles_look_up_object() to fix the above issue and simplify the code.

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-2025-2855IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht spezifizierte Angriffe durchzuführen.

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

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

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

d?id=CVE-2024-47866 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48875 https://www.cve.org/CVERecord?id=CVE-2024-48875 Référence CVE CVE-2024-49504 https://www.cve.org/CVERecord?id=CVE-2024-49504 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49855 https://www.cve.org/CVERecord?id=CVE-2024-49855 Référence CVE CVE-2024-49859 https://www.cve.org/CVERecord?id=CVE-2024-49859 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49898 https://www.cve.org/CVERecord?id=CVE-2024-49898 Référence CVE CVE-2024-49899 https://www.cve.org/CVERecord?id=CVE-2024-49899 Référence CVE CVE-2024-49901 https://www.cve.org/CVERecord?id=CVE-2024-49901 Référence CVE CVE-2024-49904 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47866 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48875 https://www.cve.org/CVERecord?id=CVE-2024-48875 Référence CVE CVE-2024-49504 https://www.cve.org/CVERecord?id=CVE-2024-49504 Référence CVE CVE-2024-49568 https://www.cve.org/CVERecord?id=CVE-2024-49568 Référence CVE CVE-2024-49569 https://www.cve.org/CVERecord?id=CVE-2024-49569 Référence CVE CVE-2024-49855 https://www.cve.org/CVERecord?id=CVE-2024-49855 Référence CVE CVE-2024-49859 https://www.cve.org/CVERecord?id=CVE-2024-49859 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49888 https://www.cve.org/CVERecord?id=CVE-2024-49888 Référence CVE CVE-2024-49891 https://www.cve.org/CVERecord?id=CVE-2024-49891 Référence CVE CVE-2024-49893 https://www.cve.org/CVERecord?id=CVE-2024-49893 Référence CVE CVE-2024-49898 https://www.cve.org/CVERecord?id=CVE-2024-49898 Référence CVE CVE-2024-49899 https://www.cve.org/CVERecord?id=CVE-2024-49899 Référence CVE CVE-2024-49901 https://www.cve.org/CVERecord?id=CVE-2024-49901 Référence CVE CVE-2024-49904 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-47727 Référence CVE CVE-2024-47734 https://www.cve.org/CVERecord?id=CVE-2024-47734 Référence CVE CVE-2024-48873 https://www.cve.org/CVERecord?id=CVE-2024-48873 Référence CVE CVE-2024-48876 https://www.cve.org/CVERecord?id=CVE-2024-48876 Référence CVE CVE-2024-49855 https://www.cve.org/CVERecord?id=CVE-2024-49855 Référence CVE CVE-2024-49856 https://www.cve.org/CVERecord?id=CVE-2024-49856 Référence CVE CVE-2024-49862 https://www.cve.org/CVERecord?id=CVE-2024-49862 Référence CVE CVE-2024-49864 https://www.cve.org/CVERecord?id=CVE-2024-49864 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49885 https://www.cve.org/CVERecord?id=CVE-2024-49885 Référence CVE CVE-2024-49886 https://www.cve.org/CVERecord?id=CVE-2024-49886 Référence CVE CVE-2024-49946 https://www.cve.org/CVERecord?id=CVE-2024-49946 Référence CVE CVE-2024-49951 https://www.cve.org/CVERecord?id=CVE-2024-49951 Référence CVE CVE-2024-49953 https://www.cve.org/CVERecord?id=CVE-2024-49953 Référence CVE CVE-2024-49976 https://www.cve.org/CVERecord?id=CVE-2024-49976 Référence CVE CVE-2024-49977 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-49858 Référence CVE CVE-2024-49859 https://www.cve.org/CVERecord?id=CVE-2024-49859 Référence CVE CVE-2024-49860 https://www.cve.org/CVERecord?id=CVE-2024-49860 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49863 https://www.cve.org/CVERecord?id=CVE-2024-49863 Référence CVE CVE-2024-49865 https://www.cve.org/CVERecord?id=CVE-2024-49865 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49868 https://www.cve.org/CVERecord?id=CVE-2024-49868 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49871 https://www.cve.org/CVERecord?id=CVE-2024-49871 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=CVE-2024-49880 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 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-49860 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49862 https://www.cve.org/CVERecord?id=CVE-2024-49862 Référence CVE CVE-2024-49863 https://www.cve.org/CVERecord?id=CVE-2024-49863 Référence CVE CVE-2024-49864 https://www.cve.org/CVERecord?id=CVE-2024-49864 Référence CVE CVE-2024-49865 https://www.cve.org/CVERecord?id=CVE-2024-49865 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49868 https://www.cve.org/CVERecord?id=CVE-2024-49868 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49871 https://www.cve.org/CVERecord?id=CVE-2024-49871 Référence CVE CVE-2024-49874 https://www.cve.org/CVERecord?id=CVE-2024-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49876 https://www.cve.org/CVERecord?id=CVE-2024-49876 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 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-49861 Référence CVE CVE-2024-49862 https://www.cve.org/CVERecord?id=CVE-2024-49862 Référence CVE CVE-2024-49863 https://www.cve.org/CVERecord?id=CVE-2024-49863 Référence CVE CVE-2024-49864 https://www.cve.org/CVERecord?id=CVE-2024-49864 Référence CVE CVE-2024-49865 https://www.cve.org/CVERecord?id=CVE-2024-49865 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49868 https://www.cve.org/CVERecord?id=CVE-2024-49868 Référence CVE CVE-2024-49869 https://www.cve.org/CVERecord?id=CVE-2024-49869 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49871 https://www.cve.org/CVERecord?id=CVE-2024-49871 Référence CVE CVE-2024-49872 https://www.cve.org/CVERecord?id=CVE-2024-49872 Référence CVE CVE-2024-49873 https://www.cve.org/CVERecord?id=CVE-2024-49873 Référence CVE CVE-2024-49874 https://www.cve.org/CVERecord?id=CVE-2024-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49876 https://www.cve.org/CVERecord?id=CVE-2024-49876 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49859 Référence CVE CVE-2024-49860 https://www.cve.org/CVERecord?id=CVE-2024-49860 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49862 https://www.cve.org/CVERecord?id=CVE-2024-49862 Référence CVE CVE-2024-49863 https://www.cve.org/CVERecord?id=CVE-2024-49863 Référence CVE CVE-2024-49864 https://www.cve.org/CVERecord?id=CVE-2024-49864 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49868 https://www.cve.org/CVERecord?id=CVE-2024-49868 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49871 https://www.cve.org/CVERecord?id=CVE-2024-49871 Référence CVE CVE-2024-49874 https://www.cve.org/CVERecord?id=CVE-2024-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49876 https://www.cve.org/CVERecord?id=CVE-2024-49876 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49880 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49861 Référence CVE CVE-2024-49862 https://www.cve.org/CVERecord?id=CVE-2024-49862 Référence CVE CVE-2024-49863 https://www.cve.org/CVERecord?id=CVE-2024-49863 Référence CVE CVE-2024-49864 https://www.cve.org/CVERecord?id=CVE-2024-49864 Référence CVE CVE-2024-49865 https://www.cve.org/CVERecord?id=CVE-2024-49865 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49868 https://www.cve.org/CVERecord?id=CVE-2024-49868 Référence CVE CVE-2024-49869 https://www.cve.org/CVERecord?id=CVE-2024-49869 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49871 https://www.cve.org/CVERecord?id=CVE-2024-49871 Référence CVE CVE-2024-49872 https://www.cve.org/CVERecord?id=CVE-2024-49872 Référence CVE CVE-2024-49873 https://www.cve.org/CVERecord?id=CVE-2024-49873 Référence CVE CVE-2024-49874 https://www.cve.org/CVERecord?id=CVE-2024-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49876 https://www.cve.org/CVERecord?id=CVE-2024-49876 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49855 Référence CVE CVE-2024-49856 https://www.cve.org/CVERecord?id=CVE-2024-49856 Référence CVE CVE-2024-49858 https://www.cve.org/CVERecord?id=CVE-2024-49858 Référence CVE CVE-2024-49859 https://www.cve.org/CVERecord?id=CVE-2024-49859 Référence CVE CVE-2024-49860 https://www.cve.org/CVERecord?id=CVE-2024-49860 Référence CVE CVE-2024-49863 https://www.cve.org/CVERecord?id=CVE-2024-49863 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49868 https://www.cve.org/CVERecord?id=CVE-2024-49868 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49871 https://www.cve.org/CVERecord?id=CVE-2024-49871 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=CVE-2024-49882 Référence CVE CVE-2024-49883 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49858 Référence CVE CVE-2024-49860 https://www.cve.org/CVERecord?id=CVE-2024-49860 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49862 https://www.cve.org/CVERecord?id=CVE-2024-49862 Référence CVE CVE-2024-49863 https://www.cve.org/CVERecord?id=CVE-2024-49863 Référence CVE CVE-2024-49864 https://www.cve.org/CVERecord?id=CVE-2024-49864 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49868 https://www.cve.org/CVERecord?id=CVE-2024-49868 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49871 https://www.cve.org/CVERecord?id=CVE-2024-49871 Référence CVE CVE-2024-49874 https://www.cve.org/CVERecord?id=CVE-2024-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-49855 Référence CVE CVE-2024-49858 https://www.cve.org/CVERecord?id=CVE-2024-49858 Référence CVE CVE-2024-49860 https://www.cve.org/CVERecord?id=CVE-2024-49860 Référence CVE CVE-2024-49861 https://www.cve.org/CVERecord?id=CVE-2024-49861 Référence CVE CVE-2024-49862 https://www.cve.org/CVERecord?id=CVE-2024-49862 Référence CVE CVE-2024-49863 https://www.cve.org/CVERecord?id=CVE-2024-49863 Référence CVE CVE-2024-49864 https://www.cve.org/CVERecord?id=CVE-2024-49864 Référence CVE CVE-2024-49866 https://www.cve.org/CVERecord?id=CVE-2024-49866 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=CVE-2024-49867 Référence CVE CVE-2024-49870 https://www.cve.org/CVERecord?id=CVE-2024-49870 Référence CVE CVE-2024-49871 https://www.cve.org/CVERecord?id=CVE-2024-49871 Référence CVE CVE-2024-49874 https://www.cve.org/CVERecord?id=CVE-2024-49874 Référence CVE CVE-2024-49875 https://www.cve.org/CVERecord?id=CVE-2024-49875 Référence CVE CVE-2024-49877 https://www.cve.org/CVERecord?id=CVE-2024-49877 Référence CVE CVE-2024-49878 https://www.cve.org/CVERecord?id=CVE-2024-49878 Référence CVE CVE-2024-49879 https://www.cve.org/CVERecord?id=CVE-2024-49879 Référence CVE CVE-2024-49881 https://www.cve.org/CVERecord?id=CVE-2024-49881 Référence CVE CVE-2024-49882 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-011247Linux の 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
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 21 Oct 2024 · Last source change 11 May 2026, 20:40 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-43716
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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-43716↗Vendor CSAF · Red Hat Product Security↗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-49870 · cve.blacktree.nl