CVE-2024-35807: ext4: fix corruption during on-line resize
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 239c669edb2bffa1aa2612519b1d438ab35d6be6, 37b6a3ba793bbbae057f5b991970ebcc52cb3db5, 722d2c01b8b108f8283d1b7222209d5b2a5aa7bd.
Low priority for now. Upgrade to Linux Linux 239c669edb2bffa1aa2612519b1d438ab35d6be6, 37b6a3ba793bbbae057f5b991970ebcc52cb3db5, 722d2c01b8b108f8283d1b7222209d5b2a5aa7bd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ext4: fix corruption during on-line resize We observed a corruption during on-line resize of a file system that is larger than 16 TiB with 4k block size. With having more then 2^32 blocks resize_inode is turned off by default by mke2fs. The issue can be reproduced on a smaller file system for convenience by explicitly turning off resize_inode. An on-line resize across an 8 GiB boundary (the size of a meta block group in this setup) then leads to a corruption: dev=/dev/<some_dev> # should be >= 16 GiB mkdir -p /corruption /sbin/mke2fs -t ext4 -b 4096 -O ^resize_inode $dev $((2 * 2**21 - 2**15)) mount -t ext4 $dev /corruption dd if=/dev/zero bs=4096 of=/corruption/test count=$((2*2**21 - 4*2**15)) sha1sum /corruption/test # 79d2658b39dcfd77274e435b0934028adafaab11 /corruption/test /sbin/resize2fs $dev $((2*2**21)) # drop page cache to force reload the block from disk echo 1 > /proc/sys/vm/drop_caches sha1sum /corruption/test # 3c2abc63cbf1a94c9e6977e0fbd72cd832c4d5c3 /corruption/test 2^21 = 2^15*2^6 equals 8 GiB whereof 2^15 is the number of blocks per block group and 2^6 are the number of block groups that make a meta block group. The last checksum might be different depending on how the file is laid out across the physical blocks. The actual corruption occurs at physical block 63*2^15 = 2064384 which would be the location of the backup of the meta block group's block descriptor. During the on-line resize the file system will be converted to meta_bg starting at s_first_meta_bg which is 2 in the example - meaning all block groups after 16 GiB. However, in ext4_flex_group_add we might add block groups that are not part of the first meta block group yet. In the reproducer we achieved this by substracting the size of a whole block group from the point where the meta block group would start. This must be considered when updating the backup block group descriptors to follow the non-meta_bg layout. The fix is to add a test whether the group to add is already part of the meta block group or not.
- Published
- May 17, 2024
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 19th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- linux linux kernel4.20 and later · before 5.4.274
- linux linux kernel5.5 and later · before 5.10.215
- linux linux kernel5.11 and later · before 5.15.154
- linux linux kernel3.7 and later · before 4.19.312
- linux linux kernel6.2 and later · before 6.6.24
- linux linux kernel6.7 and later · before 6.7.12
- linux linux kernel6.8 and later · before 6.8.3
- linux linux kernel5.16 and later · before 6.1.84
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.7affected
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before 75cc31c2e7193b69f5d25650bda5bb42ed92f8a1affected · git
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before ee4e9c1976147a850f6085a13fca95bcaa00d84caffected · git
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before e8e8b197317228b5089ed9e7802dadf3ccaa027aaffected · git
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before 239c669edb2bffa1aa2612519b1d438ab35d6be6affected · git
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before fb1088d51bbaa0faec5a55d4f5818a9ab79e24dfaffected · git
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before 37b6a3ba793bbbae057f5b991970ebcc52cb3db5affected · git
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before b461910af8ba3bed80f48c2bf852686d05c6fc5caffected · git
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before 722d2c01b8b108f8283d1b7222209d5b2a5aa7bdaffected · git
- 01f795f9e0d67adeccc61a8b20c28acb45fa5fd8 and later · before a6b3bfe176e8a5b05ec4447404e412c2a3fc92ccaffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.85-1 | 6.1.85-1 |
| Debian:13 | linux | before 6.7.12-1 | 6.7.12-1 |
| Red Hat:rhel_eus:9.4::appstream | bpftool-debuginfo | before 0:7.3.0-427.76.1.el9_4 | 0:7.3.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel-matched | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel-matched | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel-matched | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-doc | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-tools-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-427.76.1.el9_4 | 0:5.14.0-427.76.1.el9_4 |
+56
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-35799May 17, 2024 · drm/amd/display: Prevent crash when disable stream22Monitor
- ← EarlierCVE-2024-35805May 17, 2024 · dm snapshot: fix lockup in dm_exception_table_exit22Monitor
- Later →CVE-2024-35809May 17, 2024 · PCI/PM: Drain runtime-idle callbacks before driver removal18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 239c669edb2bffa1aa2612519b1d438ab35d6be6 | Vendor (CNA) |
| Linux Linux | 37b6a3ba793bbbae057f5b991970ebcc52cb3db5 | Vendor (CNA) |
| Linux Linux | 722d2c01b8b108f8283d1b7222209d5b2a5aa7bd | Vendor (CNA) |
| Linux Linux | 75cc31c2e7193b69f5d25650bda5bb42ed92f8a1 | Vendor (CNA) |
| Linux Linux | a6b3bfe176e8a5b05ec4447404e412c2a3fc92cc | Vendor (CNA) |
| Linux Linux | b461910af8ba3bed80f48c2bf852686d05c6fc5c | Vendor (CNA) |
| Linux Linux | e8e8b197317228b5089ed9e7802dadf3ccaa027a | Vendor (CNA) |
| Linux Linux | ee4e9c1976147a850f6085a13fca95bcaa00d84c | Vendor (CNA) |
| Linux Linux | fb1088d51bbaa0faec5a55d4f5818a9ab79e24df | Vendor (CNA) |
| debian:linux | 6.1.85-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.76.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- git.kernel.org/stable/c/37b6a3ba793bbbae057f5b991970ebcc52cb3db5
- git.kernel.org/stable/c/722d2c01b8b108f8283d1b7222209d5b2a5aa7bd
- git.kernel.org/stable/c/75cc31c2e7193b69f5d25650bda5bb42ed92f8a1
- git.kernel.org/stable/c/a6b3bfe176e8a5b05ec4447404e412c2a3fc92cc
- git.kernel.org/stable/c/b461910af8ba3bed80f48c2bf852686d05c6fc5c
- git.kernel.org/stable/c/e8e8b197317228b5089ed9e7802dadf3ccaa027a
- git.kernel.org/stable/c/ee4e9c1976147a850f6085a13fca95bcaa00d84c
- git.kernel.org/stable/c/fb1088d51bbaa0faec5a55d4f5818a9ab79e24df
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
- cert-portal.siemens.com/productcert/html/ssa-398330.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.