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

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()

Linux · Linux

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

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

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.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: As exposure requiresRemediation target: Within 365 days

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

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 13 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.

17 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 13 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.9.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.94-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.9.7-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-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-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
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-39467 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()
198 known not affected

The vendor explicitly states that these products are not 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 f2fs (Flash-Friendly File System) component of the Linux kernel. A missing sanity check on the `i_xattr_nid` during `f2fs_iget()` can lead to a slab-out-of-bounds read when accessing the `nat_bitmap` with an invalid offset. A local attacker could exploit this memory corruption vulnerability to cause a system crash, leading to a denial of service. In some scenarios, this could potentially be leveraged for privilege escalation.
Remediation
No remediation text is recorded.
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-37992

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 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: f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() syzbot reports a kernel bug as below: F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ================================================================== BUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] BUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline] BUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 Read of size 1 at addr ffff88807a58c76c by task syz-executor280/5076 CPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] current_nat_addr fs/f2fs/node.h:213 [inline] f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline] f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838 __do_sys_ioctl fs/ioctl.c:902 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is we missed to do sanity check on i_xattr_nid during f2fs_iget(), so that in fiemap() path, current_nat_addr() will access nat_bitmap w/ offset from invalid i_xattr_nid, result in triggering kasan bug report, fix it.

What

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() syzbot reports a kernel bug as below: F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ================================================================== BUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] BUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline] BUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 Read of size 1 at addr ffff88807a58c76c by task syz-executor280/5076 CPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] current_nat_addr fs/f2fs/node.h:213 [inline] f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline] f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838 __do_sys_ioctl fs/ioctl.c:902 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is we missed to do sanity check on i_xattr_nid during f2fs_iget(), so that in fiemap() path, current_nat_addr() will access nat_bitmap w/ offset from invalid i_xattr_nid, result in triggering kasan bug report, fix it.

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: f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() syzbot reports a kernel bug as below: F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ================================================================== BUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] BUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline] BUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 Read of size 1 at addr ffff88807a58c76c by task syz-executor280/5076 CPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] current_nat_addr fs/f2fs/node.h:213 [inline] f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline] f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838 __do_sys_ioctl fs/ioctl.c:902 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f The root cause is we missed to do sanity check on i_xattr_nid during f2fs_iget(), so that in fiemap() path, current_nat_addr() will access nat_bitmap w/ offset from invalid i_xattr_nid, result in triggering kasan bug report, fix it.

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:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-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-1451Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240626Security Bulletin 26 Jun 2024

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

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

d?id=CVE-2024-39298 Référence CVE CVE-2024-39301 https://www.cve.org/CVERecord?id=CVE-2024-39301 Référence CVE CVE-2024-39371 https://www.cve.org/CVERecord?id=CVE-2024-39371 Référence CVE CVE-2024-39461 https://www.cve.org/CVERecord?id=CVE-2024-39461 Référence CVE CVE-2024-39462 https://www.cve.org/CVERecord?id=CVE-2024-39462 Référence CVE CVE-2024-39463 https://www.cve.org/CVERecord?id=CVE-2024-39463 Référence CVE CVE-2024-39464 https://www.cve.org/CVERecord?id=CVE-2024-39464 Référence CVE CVE-2024-39465 https://www.cve.org/CVERecord?id=CVE-2024-39465 Référence CVE CVE-2024-39466 https://www.cve.org/CVERecord?id=CVE-2024-39466 Référence CVE CVE-2024-39467 https://www.cve.org/CVERecord?id=CVE-2024-39467 Référence CVE CVE-2024-39468 https://www.cve.org/CVERecord?id=CVE-2024-39468 Référence CVE CVE-2024-39469 https://www.cve.org/CVERecord?id=CVE-2024-39469 Référence CVE CVE-2024-39470 https://www.cve.org/CVERecord?id=CVE-2024-39470 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39473 https://www.cve.org/CVERecord?id=CVE-2024-39473 Référence CVE CVE-2024-39474 https://www.cve.org/CVERecord?id=CVE-2024-39474 Référence CVE CVE-2024-39475 https://www.cve.org/CVERecord?id=CVE-2024-39475 Référence CVE CVE-2024-39478 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39298 Référence CVE CVE-2024-39301 https://www.cve.org/CVERecord?id=CVE-2024-39301 Référence CVE CVE-2024-39371 https://www.cve.org/CVERecord?id=CVE-2024-39371 Référence CVE CVE-2024-39461 https://www.cve.org/CVERecord?id=CVE-2024-39461 Référence CVE CVE-2024-39462 https://www.cve.org/CVERecord?id=CVE-2024-39462 Référence CVE CVE-2024-39463 https://www.cve.org/CVERecord?id=CVE-2024-39463 Référence CVE CVE-2024-39464 https://www.cve.org/CVERecord?id=CVE-2024-39464 Référence CVE CVE-2024-39465 https://www.cve.org/CVERecord?id=CVE-2024-39465 Référence CVE CVE-2024-39466 https://www.cve.org/CVERecord?id=CVE-2024-39466 Référence CVE CVE-2024-39467 https://www.cve.org/CVERecord?id=CVE-2024-39467 Référence CVE CVE-2024-39468 https://www.cve.org/CVERecord?id=CVE-2024-39468 Référence CVE CVE-2024-39469 https://www.cve.org/CVERecord?id=CVE-2024-39469 Référence CVE CVE-2024-39470 https://www.cve.org/CVERecord?id=CVE-2024-39470 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39473 https://www.cve.org/CVERecord?id=CVE-2024-39473 Référence CVE CVE-2024-39474 https://www.cve.org/CVERecord?id=CVE-2024-39474 Référence CVE CVE-2024-39475 https://www.cve.org/CVERecord?id=CVE-2024-39475 Référence CVE CVE-2024-39478 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-39298 Référence CVE CVE-2024-39301 https://www.cve.org/CVERecord?id=CVE-2024-39301 Référence CVE CVE-2024-39371 https://www.cve.org/CVERecord?id=CVE-2024-39371 Référence CVE CVE-2024-39461 https://www.cve.org/CVERecord?id=CVE-2024-39461 Référence CVE CVE-2024-39462 https://www.cve.org/CVERecord?id=CVE-2024-39462 Référence CVE CVE-2024-39463 https://www.cve.org/CVERecord?id=CVE-2024-39463 Référence CVE CVE-2024-39464 https://www.cve.org/CVERecord?id=CVE-2024-39464 Référence CVE CVE-2024-39465 https://www.cve.org/CVERecord?id=CVE-2024-39465 Référence CVE CVE-2024-39466 https://www.cve.org/CVERecord?id=CVE-2024-39466 Référence CVE CVE-2024-39467 https://www.cve.org/CVERecord?id=CVE-2024-39467 Référence CVE CVE-2024-39468 https://www.cve.org/CVERecord?id=CVE-2024-39468 Référence CVE CVE-2024-39469 https://www.cve.org/CVERecord?id=CVE-2024-39469 Référence CVE CVE-2024-39470 https://www.cve.org/CVERecord?id=CVE-2024-39470 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39473 https://www.cve.org/CVERecord?id=CVE-2024-39473 Référence CVE CVE-2024-39474 https://www.cve.org/CVERecord?id=CVE-2024-39474 Référence CVE CVE-2024-39475 https://www.cve.org/CVERecord?id=CVE-2024-39475 Référence CVE CVE-2024-39478 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-38634 Référence CVE CVE-2024-38635 https://www.cve.org/CVERecord?id=CVE-2024-38635 Référence CVE CVE-2024-38637 https://www.cve.org/CVERecord?id=CVE-2024-38637 Référence CVE CVE-2024-38659 https://www.cve.org/CVERecord?id=CVE-2024-38659 Référence CVE CVE-2024-38661 https://www.cve.org/CVERecord?id=CVE-2024-38661 Référence CVE CVE-2024-38780 https://www.cve.org/CVERecord?id=CVE-2024-38780 Référence CVE CVE-2024-39276 https://www.cve.org/CVERecord?id=CVE-2024-39276 Référence CVE CVE-2024-39292 https://www.cve.org/CVERecord?id=CVE-2024-39292 Référence CVE CVE-2024-39301 https://www.cve.org/CVERecord?id=CVE-2024-39301 Référence CVE CVE-2024-39467 https://www.cve.org/CVERecord?id=CVE-2024-39467 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39475 https://www.cve.org/CVERecord?id=CVE-2024-39475 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-39484 https://www.cve.org/CVERecord?id=CVE-2024-39484 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Gestion détaillée du document le 23 août 2024 Version initiale

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

d?id=CVE-2024-38634 Référence CVE CVE-2024-38635 https://www.cve.org/CVERecord?id=CVE-2024-38635 Référence CVE CVE-2024-38637 https://www.cve.org/CVERecord?id=CVE-2024-38637 Référence CVE CVE-2024-38659 https://www.cve.org/CVERecord?id=CVE-2024-38659 Référence CVE CVE-2024-38661 https://www.cve.org/CVERecord?id=CVE-2024-38661 Référence CVE CVE-2024-38780 https://www.cve.org/CVERecord?id=CVE-2024-38780 Référence CVE CVE-2024-39276 https://www.cve.org/CVERecord?id=CVE-2024-39276 Référence CVE CVE-2024-39292 https://www.cve.org/CVERecord?id=CVE-2024-39292 Référence CVE CVE-2024-39301 https://www.cve.org/CVERecord?id=CVE-2024-39301 Référence CVE CVE-2024-39467 https://www.cve.org/CVERecord?id=CVE-2024-39467 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39475 https://www.cve.org/CVERecord?id=CVE-2024-39475 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-39482 https://www.cve.org/CVERecord?id=CVE-2024-39482 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-41011 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-38634 Référence CVE CVE-2024-38635 https://www.cve.org/CVERecord?id=CVE-2024-38635 Référence CVE CVE-2024-38637 https://www.cve.org/CVERecord?id=CVE-2024-38637 Référence CVE CVE-2024-38659 https://www.cve.org/CVERecord?id=CVE-2024-38659 Référence CVE CVE-2024-38661 https://www.cve.org/CVERecord?id=CVE-2024-38661 Référence CVE CVE-2024-38780 https://www.cve.org/CVERecord?id=CVE-2024-38780 Référence CVE CVE-2024-39276 https://www.cve.org/CVERecord?id=CVE-2024-39276 Référence CVE CVE-2024-39292 https://www.cve.org/CVERecord?id=CVE-2024-39292 Référence CVE CVE-2024-39301 https://www.cve.org/CVERecord?id=CVE-2024-39301 Référence CVE CVE-2024-39467 https://www.cve.org/CVERecord?id=CVE-2024-39467 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39475 https://www.cve.org/CVERecord?id=CVE-2024-39475 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-39482 https://www.cve.org/CVERecord?id=CVE-2024-39482 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-41011 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-38659 Référence CVE CVE-2024-38661 https://www.cve.org/CVERecord?id=CVE-2024-38661 Référence CVE CVE-2024-38662 https://www.cve.org/CVERecord?id=CVE-2024-38662 Référence CVE CVE-2024-38780 https://www.cve.org/CVERecord?id=CVE-2024-38780 Référence CVE CVE-2024-39276 https://www.cve.org/CVERecord?id=CVE-2024-39276 Référence CVE CVE-2024-39292 https://www.cve.org/CVERecord?id=CVE-2024-39292 Référence CVE CVE-2024-39298 https://www.cve.org/CVERecord?id=CVE-2024-39298 Référence CVE CVE-2024-39301 https://www.cve.org/CVERecord?id=CVE-2024-39301 Référence CVE CVE-2024-39371 https://www.cve.org/CVERecord?id=CVE-2024-39371 Référence CVE CVE-2024-39467 https://www.cve.org/CVERecord?id=CVE-2024-39467 Référence CVE CVE-2024-39468 https://www.cve.org/CVERecord?id=CVE-2024-39468 Référence CVE CVE-2024-39469 https://www.cve.org/CVERecord?id=CVE-2024-39469 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39474 https://www.cve.org/CVERecord?id=CVE-2024-39474 Référence CVE CVE-2024-39475 https://www.cve.org/CVERecord?id=CVE-2024-39475 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-39482 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-027975Linux の 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
Linux: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < c559a8d840562fbfce9f318448dda2f7d3e6d8e8, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 75c87e2ac6149abf44bdde0dd6d541763ddb0dff, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 1640dcf383cdba52be8b28d2a1a2aa7ef7a30c98, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 8c8aa473fe6eb46a4bf99f3ea2dbe52bf0c1a1f0, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < be0155202e431f3007778568a72432c68f8946ba, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 68e3cd4ecb8603936cccdc338929130045df2e57, 98e4da8ca301e062d79ae168c67e56f3c3de3ce4 < 20faaf30e55522bba2b56d9c46689233205d7717, 3.8
Fixed
Linux: < 3.8, 5.4.278 ≤ 5.4.*, 5.10.219 ≤ 5.10.*, 5.15.161 ≤ 5.15.*, 6.1.94 ≤ 6.1.*, 6.6.34 ≤ 6.6.*, 6.9.5 ≤ 6.9.*, 6.10 ≤ *
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 25 Jun 2024 · Last source change 5 Aug 2026, 11:33 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-37992
Product sourceCNA
Remediation sourceCVE/CNA references
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-37992↗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-39467 · cve.blacktree.nl