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

ext4: check dot and dotdot of dx_root before making dir indexed

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 16 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 12 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.23% 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 16 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.

19 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 15 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.10.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.106-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.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-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.8Affected, 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-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2024-42305 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ext4: check dot and dotdot of dx_root before making dir indexed
112 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 ext4 filesystem. When converting a directory to an indexed format, the system incorrectly assumes the presence of "dot" and "dotdot" entries. A local attacker could create a specially crafted filesystem image that, when processed during a rename operation, triggers an out-of-bounds access. This vulnerability can lead to a system crash, resulting in a Denial of Service (DoS).
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.
SSA-265688 · CSAF 2.0 · revision 13 · interimSiemens ProductCERTSSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1
1 known affected

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

  • SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: check dot and dotdot of dx_root before making dir indexed
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-39528

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 16 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: ext4: check dot and dotdot of dx_root before making dir indexed Syzbot reports a issue as follows: ============================================ BUG: unable to handle page fault for address: ffffed11022e24fe PGD 23ffee067 P4D 23ffee067 PUD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0 Call Trace: <TASK> make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341 ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451 ext4_rename fs/ext4/namei.c:3936 [inline] ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214 [...] ============================================ The immediate cause of this problem is that there is only one valid dentry for the block to be split during do_split, so split==0 results in out of bounds accesses to the map triggering the issue. do_split unsigned split dx_make_map count = 1 split = count/2 = 0; continued = hash2 == map[split - 1].hash; ---> map[4294967295] The maximum length of a filename is 255 and the minimum block size is 1024, so it is always guaranteed that the number of entries is greater than or equal to 2 when do_split() is called. But syzbot's crafted image has no dot and dotdot in dir, and the dentry distribution in dirblock is as follows: bus dentry1 hole dentry2 free |xx--|xx-------------|...............|xx-------------|...............| 0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024 So when renaming dentry1 increases its name_len length by 1, neither hole nor free is sufficient to hold the new dentry, and make_indexed_dir() is called. In make_indexed_dir() it is assumed that the first two entries of the dirblock must be dot and dotdot, so bus and dentry1 are left in dx_root because they are treated as dot and dotdot, and only dentry2 is moved to the new leaf block. That's why count is equal to 1. Therefore add the ext4_check_dx_root() helper function to add more sanity checks to dot and dotdot before starting the conversion to avoid the above issue.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: check dot and dotdot of dx_root before making dir indexed Syzbot reports a issue as follows: ============================================ BUG: unable to handle page fault for address: ffffed11022e24fe PGD 23ffee067 P4D 23ffee067 PUD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0 Call Trace: <TASK> make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341 ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451 ext4_rename fs/ext4/namei.c:3936 [inline] ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214 [...] ============================================ The immediate cause of this problem is that there is only one valid dentry for the block to be split during do_split, so split==0 results in out of bounds accesses to the map triggering the issue. do_split unsigned split dx_make_map count = 1 split = count/2 = 0; continued = hash2 == map[split - 1].hash; ---> map[4294967295] The maximum length of a filename is 255 and the minimum block size is 1024, so it is always guaranteed that the number of entries is greater than or equal to 2 when do_split() is called. But syzbot's crafted image has no dot and dotdot in dir, and the dentry distribution in dirblock is as follows: bus dentry1 hole dentry2 free |xx--|xx-------------|...............|xx-------------|...............| 0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024 So when renaming dentry1 increases its name_len length by 1, neither hole nor free is sufficient to hold the new dentry, and make_indexed_dir() is called. In make_indexed_dir() it is assumed that the first two entries of the dirblock must be dot and dotdot, so bus and dentry1 are left in dx_root because they are treated as dot and dotdot, and only dentry2 is moved to the new leaf block. That's why count is equal to 1. Therefore add the ext4_check_dx_root() helper function to add more sanity checks to dot and dotdot before starting the conversion to avoid the above issue.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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: ext4: check dot and dotdot of dx_root before making dir indexed Syzbot reports a issue as follows: ============================================ BUG: unable to handle page fault for address: ffffed11022e24fe PGD 23ffee067 P4D 23ffee067 PUD 0 Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 0 PID: 5079 Comm: syz-executor306 Not tainted 6.10.0-rc5-g55027e689933 #0 Call Trace: <TASK> make_indexed_dir+0xdaf/0x13c0 fs/ext4/namei.c:2341 ext4_add_entry+0x222a/0x25d0 fs/ext4/namei.c:2451 ext4_rename fs/ext4/namei.c:3936 [inline] ext4_rename2+0x26e5/0x4370 fs/ext4/namei.c:4214 [...] ============================================ The immediate cause of this problem is that there is only one valid dentry for the block to be split during do_split, so split==0 results in out of bounds accesses to the map triggering the issue. do_split unsigned split dx_make_map count = 1 split = count/2 = 0; continued = hash2 == map[split - 1].hash; ---> map[4294967295] The maximum length of a filename is 255 and the minimum block size is 1024, so it is always guaranteed that the number of entries is greater than or equal to 2 when do_split() is called. But syzbot's crafted image has no dot and dotdot in dir, and the dentry distribution in dirblock is as follows: bus dentry1 hole dentry2 free |xx--|xx-------------|...............|xx-------------|...............| 0 12 (8+248)=256 268 256 524 (8+256)=264 788 236 1024 So when renaming dentry1 increases its name_len length by 1, neither hole nor free is sufficient to hold the new dentry, and make_indexed_dir() is called. In make_indexed_dir() it is assumed that the first two entries of the dirblock must be dot and dotdot, so bus and dentry1 are left in dx_root because they are treated as dot and dotdot, and only dentry2 is moved to the new leaf block. That's why count is equal to 1. Therefore add the ext4_check_dx_root() helper function to add more sanity checks to dot and dotdot before starting the conversion to avoid the above issue.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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 → Out-of-bounds Read → 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-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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

Official authority intelligence

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

BSI · German · WID-SEC-2024-1875Linux 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 oder unbekannte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240821Security Bulletin 21 Aug 2024

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

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

d?id=CVE-2024-42295 Référence CVE CVE-2024-42296 https://www.cve.org/CVERecord?id=CVE-2024-42296 Référence CVE CVE-2024-42297 https://www.cve.org/CVERecord?id=CVE-2024-42297 Référence CVE CVE-2024-42298 https://www.cve.org/CVERecord?id=CVE-2024-42298 Référence CVE CVE-2024-42299 https://www.cve.org/CVERecord?id=CVE-2024-42299 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-42302 https://www.cve.org/CVERecord?id=CVE-2024-42302 Référence CVE CVE-2024-42303 https://www.cve.org/CVERecord?id=CVE-2024-42303 Référence CVE CVE-2024-42304 https://www.cve.org/CVERecord?id=CVE-2024-42304 Référence CVE CVE-2024-42305 https://www.cve.org/CVERecord?id=CVE-2024-42305 Référence CVE CVE-2024-42306 https://www.cve.org/CVERecord?id=CVE-2024-42306 Référence CVE CVE-2024-42307 https://www.cve.org/CVERecord?id=CVE-2024-42307 Référence CVE CVE-2024-42309 https://www.cve.org/CVERecord?id=CVE-2024-42309 Référence CVE CVE-2024-42310 https://www.cve.org/CVERecord?id=CVE-2024-42310 Référence CVE CVE-2024-42311 https://www.cve.org/CVERecord?id=CVE-2024-42311 Référence CVE CVE-2024-42312 https://www.cve.org/CVERecord?id=CVE-2024-42312 Référence CVE CVE-2024-42313 https://www.cve.org/CVERecord?id=CVE-2024-42313 Référence CVE CVE-2024-42314 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-42291 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=CVE-2024-42292 Référence CVE CVE-2024-42295 https://www.cve.org/CVERecord?id=CVE-2024-42295 Référence CVE CVE-2024-42296 https://www.cve.org/CVERecord?id=CVE-2024-42296 Référence CVE CVE-2024-42297 https://www.cve.org/CVERecord?id=CVE-2024-42297 Référence CVE CVE-2024-42299 https://www.cve.org/CVERecord?id=CVE-2024-42299 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-42302 https://www.cve.org/CVERecord?id=CVE-2024-42302 Référence CVE CVE-2024-42304 https://www.cve.org/CVERecord?id=CVE-2024-42304 Référence CVE CVE-2024-42305 https://www.cve.org/CVERecord?id=CVE-2024-42305 Référence CVE CVE-2024-42306 https://www.cve.org/CVERecord?id=CVE-2024-42306 Référence CVE CVE-2024-42307 https://www.cve.org/CVERecord?id=CVE-2024-42307 Référence CVE CVE-2024-42309 https://www.cve.org/CVERecord?id=CVE-2024-42309 Référence CVE CVE-2024-42310 https://www.cve.org/CVERecord?id=CVE-2024-42310 Référence CVE CVE-2024-42311 https://www.cve.org/CVERecord?id=CVE-2024-42311 Référence CVE CVE-2024-42312 https://www.cve.org/CVERecord?id=CVE-2024-42312 Référence CVE CVE-2024-42313 https://www.cve.org/CVERecord?id=CVE-2024-42313 Référence CVE CVE-2024-42314 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42295 Référence CVE CVE-2024-42296 https://www.cve.org/CVERecord?id=CVE-2024-42296 Référence CVE CVE-2024-42297 https://www.cve.org/CVERecord?id=CVE-2024-42297 Référence CVE CVE-2024-42298 https://www.cve.org/CVERecord?id=CVE-2024-42298 Référence CVE CVE-2024-42299 https://www.cve.org/CVERecord?id=CVE-2024-42299 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-42302 https://www.cve.org/CVERecord?id=CVE-2024-42302 Référence CVE CVE-2024-42303 https://www.cve.org/CVERecord?id=CVE-2024-42303 Référence CVE CVE-2024-42304 https://www.cve.org/CVERecord?id=CVE-2024-42304 Référence CVE CVE-2024-42305 https://www.cve.org/CVERecord?id=CVE-2024-42305 Référence CVE CVE-2024-42306 https://www.cve.org/CVERecord?id=CVE-2024-42306 Référence CVE CVE-2024-42307 https://www.cve.org/CVERecord?id=CVE-2024-42307 Référence CVE CVE-2024-42309 https://www.cve.org/CVERecord?id=CVE-2024-42309 Référence CVE CVE-2024-42310 https://www.cve.org/CVERecord?id=CVE-2024-42310 Référence CVE CVE-2024-42311 https://www.cve.org/CVERecord?id=CVE-2024-42311 Référence CVE CVE-2024-42312 https://www.cve.org/CVERecord?id=CVE-2024-42312 Référence CVE CVE-2024-42313 https://www.cve.org/CVERecord?id=CVE-2024-42313 Référence CVE CVE-2024-42314 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42290 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=CVE-2024-42292 Référence CVE CVE-2024-42295 https://www.cve.org/CVERecord?id=CVE-2024-42295 Référence CVE CVE-2024-42296 https://www.cve.org/CVERecord?id=CVE-2024-42296 Référence CVE CVE-2024-42297 https://www.cve.org/CVERecord?id=CVE-2024-42297 Référence CVE CVE-2024-42299 https://www.cve.org/CVERecord?id=CVE-2024-42299 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-42302 https://www.cve.org/CVERecord?id=CVE-2024-42302 Référence CVE CVE-2024-42304 https://www.cve.org/CVERecord?id=CVE-2024-42304 Référence CVE CVE-2024-42305 https://www.cve.org/CVERecord?id=CVE-2024-42305 Référence CVE CVE-2024-42306 https://www.cve.org/CVERecord?id=CVE-2024-42306 Référence CVE CVE-2024-42309 https://www.cve.org/CVERecord?id=CVE-2024-42309 Référence CVE CVE-2024-42310 https://www.cve.org/CVERecord?id=CVE-2024-42310 Référence CVE CVE-2024-42311 https://www.cve.org/CVERecord?id=CVE-2024-42311 Référence CVE CVE-2024-42312 https://www.cve.org/CVERecord?id=CVE-2024-42312 Référence CVE CVE-2024-42313 https://www.cve.org/CVERecord?id=CVE-2024-42313 Référence CVE CVE-2024-42318 https://www.cve.org/CVERecord?id=CVE-2024-42318 Référence CVE CVE-2024-43817 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42290 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=CVE-2024-42292 Référence CVE CVE-2024-42295 https://www.cve.org/CVERecord?id=CVE-2024-42295 Référence CVE CVE-2024-42296 https://www.cve.org/CVERecord?id=CVE-2024-42296 Référence CVE CVE-2024-42297 https://www.cve.org/CVERecord?id=CVE-2024-42297 Référence CVE CVE-2024-42299 https://www.cve.org/CVERecord?id=CVE-2024-42299 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-42302 https://www.cve.org/CVERecord?id=CVE-2024-42302 Référence CVE CVE-2024-42304 https://www.cve.org/CVERecord?id=CVE-2024-42304 Référence CVE CVE-2024-42305 https://www.cve.org/CVERecord?id=CVE-2024-42305 Référence CVE CVE-2024-42306 https://www.cve.org/CVERecord?id=CVE-2024-42306 Référence CVE CVE-2024-42309 https://www.cve.org/CVERecord?id=CVE-2024-42309 Référence CVE CVE-2024-42310 https://www.cve.org/CVERecord?id=CVE-2024-42310 Référence CVE CVE-2024-42311 https://www.cve.org/CVERecord?id=CVE-2024-42311 Référence CVE CVE-2024-42312 https://www.cve.org/CVERecord?id=CVE-2024-42312 Référence CVE CVE-2024-42313 https://www.cve.org/CVERecord?id=CVE-2024-42313 Référence CVE CVE-2024-42318 https://www.cve.org/CVERecord?id=CVE-2024-42318 Référence CVE CVE-2024-43817 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42287 Référence CVE CVE-2024-42288 https://www.cve.org/CVERecord?id=CVE-2024-42288 Référence CVE CVE-2024-42289 https://www.cve.org/CVERecord?id=CVE-2024-42289 Référence CVE CVE-2024-42290 https://www.cve.org/CVERecord?id=CVE-2024-42290 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=CVE-2024-42292 Référence CVE CVE-2024-42295 https://www.cve.org/CVERecord?id=CVE-2024-42295 Référence CVE CVE-2024-42297 https://www.cve.org/CVERecord?id=CVE-2024-42297 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-42304 https://www.cve.org/CVERecord?id=CVE-2024-42304 Référence CVE CVE-2024-42305 https://www.cve.org/CVERecord?id=CVE-2024-42305 Référence CVE CVE-2024-42306 https://www.cve.org/CVERecord?id=CVE-2024-42306 Référence CVE CVE-2024-42309 https://www.cve.org/CVERecord?id=CVE-2024-42309 Référence CVE CVE-2024-42310 https://www.cve.org/CVERecord?id=CVE-2024-42310 Référence CVE CVE-2024-42311 https://www.cve.org/CVERecord?id=CVE-2024-42311 Référence CVE CVE-2024-42313 https://www.cve.org/CVERecord?id=CVE-2024-42313 Référence CVE CVE-2024-43829 https://www.cve.org/CVERecord?id=CVE-2024-43829 Référence CVE CVE-2024-43830 https://www.cve.org/CVERecord?id=CVE-2024-43830 Référence CVE CVE-2024-43835 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42288 Référence CVE CVE-2024-42289 https://www.cve.org/CVERecord?id=CVE-2024-42289 Référence CVE CVE-2024-42290 https://www.cve.org/CVERecord?id=CVE-2024-42290 Référence CVE CVE-2024-42292 https://www.cve.org/CVERecord?id=CVE-2024-42292 Référence CVE CVE-2024-42295 https://www.cve.org/CVERecord?id=CVE-2024-42295 Référence CVE CVE-2024-42297 https://www.cve.org/CVERecord?id=CVE-2024-42297 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-42302 https://www.cve.org/CVERecord?id=CVE-2024-42302 Référence CVE CVE-2024-42304 https://www.cve.org/CVERecord?id=CVE-2024-42304 Référence CVE CVE-2024-42305 https://www.cve.org/CVERecord?id=CVE-2024-42305 Référence CVE CVE-2024-42306 https://www.cve.org/CVERecord?id=CVE-2024-42306 Référence CVE CVE-2024-42308 https://www.cve.org/CVERecord?id=CVE-2024-42308 Référence CVE CVE-2024-42309 https://www.cve.org/CVERecord?id=CVE-2024-42309 Référence CVE CVE-2024-42310 https://www.cve.org/CVERecord?id=CVE-2024-42310 Référence CVE CVE-2024-42311 https://www.cve.org/CVERecord?id=CVE-2024-42311 Référence CVE CVE-2024-42312 https://www.cve.org/CVERecord?id=CVE-2024-42312 Référence CVE CVE-2024-42313 https://www.cve.org/CVERecord?id=CVE-2024-42313 Référence CVE CVE-2024-43828 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-41087 Référence CVE CVE-2024-42154 https://www.cve.org/CVERecord?id=CVE-2024-42154 Référence CVE CVE-2024-42243 https://www.cve.org/CVERecord?id=CVE-2024-42243 Référence CVE CVE-2024-42252 https://www.cve.org/CVERecord?id=CVE-2024-42252 Référence CVE CVE-2024-42259 https://www.cve.org/CVERecord?id=CVE-2024-42259 Référence CVE CVE-2024-42265 https://www.cve.org/CVERecord?id=CVE-2024-42265 Référence CVE CVE-2024-42294 https://www.cve.org/CVERecord?id=CVE-2024-42294 Référence CVE CVE-2024-42301 https://www.cve.org/CVERecord?id=CVE-2024-42301 Référence CVE CVE-2024-42304 https://www.cve.org/CVERecord?id=CVE-2024-42304 Référence CVE CVE-2024-42305 https://www.cve.org/CVERecord?id=CVE-2024-42305 Référence CVE CVE-2024-42306 https://www.cve.org/CVERecord?id=CVE-2024-42306 Référence CVE CVE-2024-43828 https://www.cve.org/CVERecord?id=CVE-2024-43828 Référence CVE CVE-2024-43832 https://www.cve.org/CVERecord?id=CVE-2024-43832 Référence CVE CVE-2024-43835 https://www.cve.org/CVERecord?id=CVE-2024-43835 Référence CVE CVE-2024-43845 https://www.cve.org/CVERecord?id=CVE-2024-43845 Référence CVE CVE-2024-43870 https://www.cve.org/CVERecord?id=CVE-2024-43870 Référence CVE CVE-2024-43884 https://www.cve.org/CVERecord?id=CVE-2024-43884 Référence CVE CVE-2024-43886 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028584Linux の 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 17 Aug 2024 · Last source change 12 May 2026, 11:56 UTC · CWE-125 · Out-of-bounds Read

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-39528
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-39528↗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-42305 · cve.blacktree.nl