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

nilfs2: prevent use of deleted inode

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.26% 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.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.123-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.8-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-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-53690 · CSAF 2.0 · revision 63 · interimSUSE Product Security TeamCVE-2024-53690
15 known affected

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

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
In the Linux kernel, the following vulnerability has been resolved: nilfs2: prevent use of deleted inode syzbot reported a WARNING in nilfs_rmdir. [1] Because the inode bitmap is corrupted, an inode with an inode number that should exist as a ".nilfs" file was reassigned by nilfs_mkdir for "file0", causing an inode duplication during execution. And this causes an underflow of i_nlink in rmdir operations. The inode is used twice by the same task to unmount and remove directories ".nilfs" and "file0", it trigger warning in nilfs_rmdir. Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means that this inode has been deleted, and iput is executed to reclaim it. [1] WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407 ... Call Trace: nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394 do_rmdir+0x3b5/0x580 fs/namei.c:4453 __do_sys_rmdir fs/namei.c:4472 [inline] __se_sys_rmdir fs/namei.c:4470 [inline] __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f
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-52033

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: nilfs2: prevent use of deleted inode syzbot reported a WARNING in nilfs_rmdir. [1] Because the inode bitmap is corrupted, an inode with an inode number that should exist as a ".nilfs" file was reassigned by nilfs_mkdir for "file0", causing an inode duplication during execution. And this causes an underflow of i_nlink in rmdir operations. The inode is used twice by the same task to unmount and remove directories ".nilfs" and "file0", it trigger warning in nilfs_rmdir. Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means that this inode has been deleted, and iput is executed to reclaim it. [1] WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407 ... Call Trace: <TASK> nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394 do_rmdir+0x3b5/0x580 fs/namei.c:4453 __do_sys_rmdir fs/namei.c:4472 [inline] __se_sys_rmdir fs/namei.c:4470 [inline] __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

What

In the Linux kernel, the following vulnerability has been resolved: nilfs2: prevent use of deleted inode syzbot reported a WARNING in nilfs_rmdir. [1] Because the inode bitmap is corrupted, an inode with an inode number that should exist as a ".nilfs" file was reassigned by nilfs_mkdir for "file0", causing an inode duplication during execution. And this causes an underflow of i_nlink in rmdir operations. The inode is used twice by the same task to unmount and remove directories ".nilfs" and "file0", it trigger warning in nilfs_rmdir. Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means that this inode has been deleted, and iput is executed to reclaim it. [1] WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407 ... Call Trace: <TASK> nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394 do_rmdir+0x3b5/0x580 fs/namei.c:4453 __do_sys_rmdir fs/namei.c:4472 [inline] __se_sys_rmdir fs/namei.c:4470 [inline] __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: nilfs2: prevent use of deleted inode syzbot reported a WARNING in nilfs_rmdir. [1] Because the inode bitmap is corrupted, an inode with an inode number that should exist as a ".nilfs" file was reassigned by nilfs_mkdir for "file0", causing an inode duplication during execution. And this causes an underflow of i_nlink in rmdir operations. The inode is used twice by the same task to unmount and remove directories ".nilfs" and "file0", it trigger warning in nilfs_rmdir. Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means that this inode has been deleted, and iput is executed to reclaim it. [1] WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407 ... Call Trace: <TASK> nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394 do_rmdir+0x3b5/0x580 fs/namei.c:4453 __do_sys_rmdir fs/namei.c:4472 [inline] __se_sys_rmdir fs/namei.c:4470 [inline] __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
A

Official authority intelligence

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

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-2025-AVI-0366Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53236 https://www.cve.org/CVERecord?id=CVE-2024-53236 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=CVE-2024-53680 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-55881 https://www.cve.org/CVERecord?id=CVE-2024-55881 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56369 https://www.cve.org/CVERecord?id=CVE-2024-56369 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 https://www.cve.org/CVERecord?id=CVE-2024-56532 Référence CVE CVE-2024-56533 https://www.cve.org/CVERecord?id=CVE-2024-56533 Référence CVE CVE-2024-56538 https://www.cve.org/CVERecord?id=CVE-2024-56538 Référence CVE CVE-2024-56539 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-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53236 https://www.cve.org/CVERecord?id=CVE-2024-53236 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=CVE-2024-53680 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-55881 https://www.cve.org/CVERecord?id=CVE-2024-55881 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56369 https://www.cve.org/CVERecord?id=CVE-2024-56369 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 https://www.cve.org/CVERecord?id=CVE-2024-56532 Référence CVE CVE-2024-56533 https://www.cve.org/CVERecord?id=CVE-2024-56533 Référence CVE CVE-2024-56538 https://www.cve.org/CVERecord?id=CVE-2024-56538 Référence CVE CVE-2024-56539 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-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=CVE-2024-53680 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-55881 https://www.cve.org/CVERecord?id=CVE-2024-55881 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56369 https://www.cve.org/CVERecord?id=CVE-2024-56369 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 https://www.cve.org/CVERecord?id=CVE-2024-56532 Référence CVE CVE-2024-56533 https://www.cve.org/CVERecord?id=CVE-2024-56533 Référence CVE CVE-2024-56539 https://www.cve.org/CVERecord?id=CVE-2024-56539 Référence CVE CVE-2024-56548 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-53214 Référence CVE CVE-2024-53215 https://www.cve.org/CVERecord?id=CVE-2024-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=CVE-2024-53680 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-55881 https://www.cve.org/CVERecord?id=CVE-2024-55881 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56369 https://www.cve.org/CVERecord?id=CVE-2024-56369 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 https://www.cve.org/CVERecord?id=CVE-2024-56532 Référence CVE CVE-2024-56533 https://www.cve.org/CVERecord?id=CVE-2024-56533 Référence CVE CVE-2024-56539 https://www.cve.org/CVERecord?id=CVE-2024-56539 Référence CVE CVE-2024-56548 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-52332 Référence CVE CVE-2024-53104 https://www.cve.org/CVERecord?id=CVE-2024-53104 Référence CVE CVE-2024-53140 https://www.cve.org/CVERecord?id=CVE-2024-53140 Référence CVE CVE-2024-53179 https://www.cve.org/CVERecord?id=CVE-2024-53179 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=CVE-2024-53680 Référence CVE CVE-2024-53681 https://www.cve.org/CVERecord?id=CVE-2024-53681 Référence CVE CVE-2024-53682 https://www.cve.org/CVERecord?id=CVE-2024-53682 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53687 https://www.cve.org/CVERecord?id=CVE-2024-53687 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-54191 https://www.cve.org/CVERecord?id=CVE-2024-54191 Référence CVE CVE-2024-54193 https://www.cve.org/CVERecord?id=CVE-2024-54193 Référence CVE CVE-2024-54455 https://www.cve.org/CVERecord?id=CVE-2024-54455 Référence CVE CVE-2024-54460 https://www.cve.org/CVERecord?id=CVE-2024-54460 Référence CVE CVE-2024-54680 https://www.cve.org/CVERecord?id=CVE-2024-54680 Référence CVE CVE-2024-54683 https://www.cve.org/CVERecord?id=CVE-2024-54683 Référence CVE CVE-2024-55639 https://www.cve.org/CVERecord?id=CVE-2024-55639 Référence CVE CVE-2024-55641 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-53215 Référence CVE CVE-2024-53217 https://www.cve.org/CVERecord?id=CVE-2024-53217 Référence CVE CVE-2024-53224 https://www.cve.org/CVERecord?id=CVE-2024-53224 Référence CVE CVE-2024-53226 https://www.cve.org/CVERecord?id=CVE-2024-53226 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-54680 https://www.cve.org/CVERecord?id=CVE-2024-54680 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 https://www.cve.org/CVERecord?id=CVE-2024-56532 Référence CVE CVE-2024-56533 https://www.cve.org/CVERecord?id=CVE-2024-56533 Référence CVE CVE-2024-56539 https://www.cve.org/CVERecord?id=CVE-2024-56539 Référence CVE CVE-2024-56548 https://www.cve.org/CVERecord?id=CVE-2024-56548 Référence CVE CVE-2024-56549 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-53231 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-53680 https://www.cve.org/CVERecord?id=CVE-2024-53680 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-54031 https://www.cve.org/CVERecord?id=CVE-2024-54031 Référence CVE CVE-2024-55881 https://www.cve.org/CVERecord?id=CVE-2024-55881 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56369 https://www.cve.org/CVERecord?id=CVE-2024-56369 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 https://www.cve.org/CVERecord?id=CVE-2024-56532 Référence CVE CVE-2024-56533 https://www.cve.org/CVERecord?id=CVE-2024-56533 Référence CVE CVE-2024-56539 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-53227 Référence CVE CVE-2024-53229 https://www.cve.org/CVERecord?id=CVE-2024-53229 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53236 https://www.cve.org/CVERecord?id=CVE-2024-53236 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-54680 https://www.cve.org/CVERecord?id=CVE-2024-54680 Référence CVE CVE-2024-55639 https://www.cve.org/CVERecord?id=CVE-2024-55639 Référence CVE CVE-2024-55881 https://www.cve.org/CVERecord?id=CVE-2024-55881 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56369 https://www.cve.org/CVERecord?id=CVE-2024-56369 Référence CVE CVE-2024-56372 https://www.cve.org/CVERecord?id=CVE-2024-56372 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 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-53203 Référence CVE CVE-2024-53227 https://www.cve.org/CVERecord?id=CVE-2024-53227 Référence CVE CVE-2024-53230 https://www.cve.org/CVERecord?id=CVE-2024-53230 Référence CVE CVE-2024-53231 https://www.cve.org/CVERecord?id=CVE-2024-53231 Référence CVE CVE-2024-53232 https://www.cve.org/CVERecord?id=CVE-2024-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53236 https://www.cve.org/CVERecord?id=CVE-2024-53236 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-54680 https://www.cve.org/CVERecord?id=CVE-2024-54680 Référence CVE CVE-2024-55639 https://www.cve.org/CVERecord?id=CVE-2024-55639 Référence CVE CVE-2024-55881 https://www.cve.org/CVERecord?id=CVE-2024-55881 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56369 https://www.cve.org/CVERecord?id=CVE-2024-56369 Référence CVE CVE-2024-56372 https://www.cve.org/CVERecord?id=CVE-2024-56372 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 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-53232 Référence CVE CVE-2024-53233 https://www.cve.org/CVERecord?id=CVE-2024-53233 Référence CVE CVE-2024-53234 https://www.cve.org/CVERecord?id=CVE-2024-53234 Référence CVE CVE-2024-53236 https://www.cve.org/CVERecord?id=CVE-2024-53236 Référence CVE CVE-2024-53237 https://www.cve.org/CVERecord?id=CVE-2024-53237 Référence CVE CVE-2024-53239 https://www.cve.org/CVERecord?id=CVE-2024-53239 Référence CVE CVE-2024-53240 https://www.cve.org/CVERecord?id=CVE-2024-53240 Référence CVE CVE-2024-53241 https://www.cve.org/CVERecord?id=CVE-2024-53241 Référence CVE CVE-2024-53685 https://www.cve.org/CVERecord?id=CVE-2024-53685 Référence CVE CVE-2024-53690 https://www.cve.org/CVERecord?id=CVE-2024-53690 Référence CVE CVE-2024-54680 https://www.cve.org/CVERecord?id=CVE-2024-54680 Référence CVE CVE-2024-55639 https://www.cve.org/CVERecord?id=CVE-2024-55639 Référence CVE CVE-2024-55881 https://www.cve.org/CVERecord?id=CVE-2024-55881 Référence CVE CVE-2024-55916 https://www.cve.org/CVERecord?id=CVE-2024-55916 Référence CVE CVE-2024-56369 https://www.cve.org/CVERecord?id=CVE-2024-56369 Référence CVE CVE-2024-56372 https://www.cve.org/CVERecord?id=CVE-2024-56372 Référence CVE CVE-2024-56531 https://www.cve.org/CVERecord?id=CVE-2024-56531 Référence CVE CVE-2024-56532 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-029083Linux の 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: < 2.6.30, 5.4.289 ≤ 5.4.*, 5.10.233 ≤ 5.10.*, 5.15.176 ≤ 5.15.*, 6.1.122 ≤ 6.1.*, 6.6.68 ≤ 6.6.*, 6.12.7 ≤ 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 11 May 2026, 20:53 UTC · CWE not yet assigned

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-52033
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

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-52033↗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-53690 · cve.blacktree.nl