cve.bz

CVE-2024-39469 linux linux kernel

7.1 highEPSS 0.3%Fix available

High (7.1) in linux linux kernel. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errors The error handling in nilfs_empty_dir() when a directory folio/page read fails is incorrect, as in the old ext2 implementation, and if the folio/page cannot be read or nilfs_check_folio() fails, it will falsely determine the directory as empty and corrupt the file system. In addition, since nilfs_empty_dir() does not immediately return on a failed folio/page read, but continues to loop, this can cause a long loop with I/O if i_size of the directory's inode is also corrupted, causing the log writer thread to wait and hang, as reported by syzbot. Fix these issues by making nilfs_empty_dir() immediately return a false value (0) if it fails to get a directory folio/page.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-09-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-39469 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-39469?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-39469?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-39469 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux2.6.30 and later

Fixed in

ProductRelease lineFixed in
Linux4.194.19.317
Linux5.45.4.279
Linux5.105.10.221
Linux5.155.15.162
Linux6.16.1.95
Linux6.66.6.35
Linux6.96.9.5
Linuxlater releases6.10

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux5.10.221-1DSA-5730-1
Debian11linux-6.16.1.119-1~deb11u1DLA-4008-1
Debian12linux6.1.99-1DEBIAN-CVE-2024-39469 DSA-5731-1
Debian13, 14linux6.9.7-1DEBIAN-CVE-2024-39469
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2024-39469
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2024-39469
Ubuntu20.04:LTSlinux5.4.0-195.215UBUNTU-CVE-2024-39469 USN-7003-1
Ubuntu20.04:LTSlinux-aws5.4.0-1132.142UBUNTU-CVE-2024-39469 USN-7003-1
Ubuntu20.04:LTSlinux-aws-5.155.15.0-1069.75~20.04.1UBUNTU-CVE-2024-39469 USN-7007-1
Ubuntu20.04:LTSlinux-azure5.4.0-1137.144UBUNTU-CVE-2024-39469 USN-7003-1
Ubuntu20.04:LTSlinux-azure-5.155.15.0-1072.81~20.04.1UBUNTU-CVE-2024-39469 USN-7009-1
Ubuntu20.04:LTSlinux-azure-fde-5.155.15.0-1072.81~20.04.1.1USN-7009-2
Ubuntu20.04:LTSlinux-bluefield5.4.0-1092.99UBUNTU-CVE-2024-39469 USN-7003-1
Ubuntu20.04:LTSlinux-gcp5.4.0-1136.145UBUNTU-CVE-2024-39469 USN-7003-1
Ubuntu20.04:LTSlinux-gcp-5.155.15.0-1068.76~20.04.1UBUNTU-CVE-2024-39469 USN-7007-1
Ubuntu20.04:LTSlinux-gke, linux-riscv, linux-raspi2 and 24 moreno fix listedUBUNTU-CVE-2024-39469
72 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 15 SP5, Linux Enterprise Live Patching 15 SP5, Linux Enterprise Micro 5.5 and 2 morekernel-default5.14.21-150500.55.73.1SUSE-SU-2024:2939-1
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6, Linux Enterprise Module for Legacy 15 SP6 and 1 morekernel-default6.4.0-150600.23.14.2SUSE-SU-2024:2571-1
SUSELinux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5-RT_Update_171-150500.11.3.1SUSE-SU-2024:2394-1
SUSELinux Enterprise Live Patching 15 SP5kernel-livepatch-SLE15-SP5_Update_171-150500.11.3.1SUSE-SU-2024:2939-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_11-150600.1.5.1SUSE-SU-2024:2973-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_21-150600.13.3.2SUSE-SU-2024:2571-1
SUSELinux Enterprise Micro 5.5kernel-rt, kernel-source-rt5.14.21-150500.13.61.1SUSE-SU-2024:2394-1
SUSELinux Enterprise Micro 5.5, Linux Enterprise Module for Basesystem 15 SP5kernel-default-base5.14.21-150500.55.73.1.150500.6.33.8SUSE-SU-2024:2939-1
SUSELinux Enterprise Module for Basesystem 15 SP5kernel-64kb, kernel-source, kernel-default and 1 more5.14.21-150500.55.73.1SUSE-SU-2024:2939-1
SUSELinux Enterprise Module for Basesystem 15 SP6kernel-64kb6.4.0-150600.23.14.1SUSE-SU-2024:2571-1
SUSELinux Enterprise Module for Basesystem 15 SP6kernel-default-base6.4.0-150600.23.14.2.150600.12.4.3SUSE-SU-2024:2571-1
SUSELinux Enterprise Module for Basesystem 15 SP6kernel-source, kernel-default, kernel-zfcpdump6.4.0-150600.23.14.2SUSE-SU-2024:2571-1
11 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 15.5dtb-aarch64, kernel-64kb, kernel-syms and 7 more5.14.21-150500.55.73.1SUSE-SU-2024:2939-1
openSUSELeap 15.5kernel-azure, kernel-syms-azure, kernel-source-azure5.14.21-150500.33.60.1SUSE-SU-2024:2372-1
openSUSELeap 15.5kernel-docs5.14.21-150500.55.73.2SUSE-SU-2024:2939-1
openSUSELeap 15.5kernel-rt, kernel-syms-rt, kernel-rt_debug and 1 more5.14.21-150500.13.61.1SUSE-SU-2024:2394-1
openSUSELeap 15.5, Leap Micro 5.5kernel-default-base5.14.21-150500.55.73.1.150500.6.33.8SUSE-SU-2024:2939-1
openSUSELeap 15.6dtb-aarch64, kernel-64kb6.4.0-150600.23.14.1SUSE-SU-2024:2571-1
openSUSELeap 15.6kernel-azure, kernel-source-azure6.4.0-150600.8.8.2SUSE-SU-2024:2896-1
openSUSELeap 15.6kernel-default-base6.4.0-150600.23.14.2.150600.12.4.3SUSE-SU-2024:2571-1
openSUSELeap 15.6kernel-docs, kernel-syms, kernel-debug and 6 more6.4.0-150600.23.14.2SUSE-SU-2024:2571-1
openSUSELeap 15.6kernel-rt, kernel-syms-rt, kernel-rt_debug and 1 more6.4.0-150600.10.5.1SUSE-SU-2024:2973-1
openSUSELeap 15.6kernel-syms-azure6.4.0-150600.8.8.1SUSE-SU-2024:2896-1
openSUSELeap Micro 5.5kernel-default5.14.21-150500.55.73.1SUSE-SU-2024:2939-1
Alpaquita23linux-lts6.1.97-r0BELL-CVE-2024-39469
Alpaquita25, streamlinux-lts6.12.41-r0BELL-CVE-2024-39469

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A flaw of low impact was found in the Linux kernel's nilfs2 file system code. When a directory folio/page read fails inside nilfs_empty_dir(), the error is mishandled: the function falsely judges the directory as empty, which can corrupt the file system, and because it does not immediately return after a failed read but keeps looping, it can enter a long loop performing I/O when the directory inode's i_size is also corrupted, causing the nilfs2 log writer thread to wait and hang. Triggering this issue requires local access to a system with a nilfs2 file system that is experiencing read errors or corrupted metadata. Red Hat assessed this flaw as Low impact with a CVSSv3 score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), reflecting availability impact only, while NIST and the CVE.org record scored it 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H) by additionally counting integrity impact; the difference reflects the more limited practical consequences Red Hat attributes to the misjudged empty-directory condition. All current Red Hat product entries for this flaw are marked not affected, including every maintained Red Hat Enterprise Linux kernel and kernel-rt stream, the hosted OpenShift offerings, and Fedora: the vulnerable nilfs2 code is not built into the Red Hat Enterprise Linux kernels, so the affected code path is not present in shipped Red Hat products.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-39469.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-25-226-07Siemens Third-Party Components in SINEC OS2025-08-12Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and Facilitiesnone listednone listed
ICSA-23-348-10Siemens SIMATIC S7-15002023-12-12Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and FacilitiesSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0), SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0), SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) and 2 morenone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

References

Check your stackJSON