CVE-2024-47700: ext4: check stripe size compatibility on remount as well
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.22% (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 297615e992bbb30a55c158141086be6505d5d722, a31b712f75445d52fc0451dc54fd7b16a552cb7c, ee85e0938aa8f9846d21e4d302c3cf6a2a75110d; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.56.1-5; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.56.1-5.
Low priority for now. Upgrade to Linux Linux 297615e992bbb30a55c158141086be6505d5d722, a31b712f75445d52fc0451dc54fd7b16a552cb7c, ee85e0938aa8f9846d21e4d302c3cf6a2a75110d; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.56.1-5; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.56.1-5 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: check stripe size compatibility on remount as well We disable stripe size in __ext4_fill_super if it is not a multiple of the cluster ratio however this check is missed when trying to remount. This can leave us with cases where stripe < cluster_ratio after remount:set making EXT4_B2C(sbi->s_stripe) become 0 that can cause some unforeseen bugs like divide by 0. Fix that by adding the check in remount path as well.
- Published
- Oct 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- CWE-369
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.5 and later · before 6.6.54
- linux linux kernel6.7 and later · before 6.10.13
- linux linux kernel6.11 and later · before 6.11.2
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
- 6.5affected
- c3defd99d58cbdd132bd197714e5523dac976b66 and later · before faeff8b1ee2eaa5969c8e994d66c3337298cefedaffected · git
- c3defd99d58cbdd132bd197714e5523dac976b66 and later · before 297615e992bbb30a55c158141086be6505d5d722affected · git
- c3defd99d58cbdd132bd197714e5523dac976b66 and later · before a31b712f75445d52fc0451dc54fd7b16a552cb7caffected · git
- c3defd99d58cbdd132bd197714e5523dac976b66 and later · before ee85e0938aa8f9846d21e4d302c3cf6a2a75110daffected · git
- before 6.5not affected · semver
- 6.6.54 and later · up to and including 6.6.*not affected · semver
- 6.10.13 and later · up to and including 6.10.*not affected · semver
- 6.11.2 and later · up to and including 6.11.*not affected · semver
- 6.12 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.11.2-1 | 6.11.2-1 |
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-47695Oct 21, 2024 · RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds31Monitor
- ← EarlierCVE-2024-47698Oct 21, 2024 · drivers: media: dvb-frontends/rtl2832: fix an out-of-bounds write error31Monitor
- Later →CVE-2024-47703Oct 21, 2024 · bpf, lsm: Add check for BPF LSM return value22Monitor
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 | 297615e992bbb30a55c158141086be6505d5d722 | Vendor (CNA) |
| Linux Linux | a31b712f75445d52fc0451dc54fd7b16a552cb7c | Vendor (CNA) |
| Linux Linux | ee85e0938aa8f9846d21e4d302c3cf6a2a75110d | Vendor (CNA) |
| Linux Linux | faeff8b1ee2eaa5969c8e994d66c3337298cefed | Vendor (CNA) |
| azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 | 6.6.56.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 | 6.6.56.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.11.2-1 · Debian:13 | 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.
- CVE-2024-26945173 days apartcrypto: iaa - Fix nr_cpus < nr_iaa case33Monitor
- CVE-2024-498920 days apartdrm/amd/display: Initialize get_bytes_per_element's default to 122Monitor
- CVE-2024-498990 days apartdrm/amd/display: Initialize denominators' default to 122Monitor
- CVE-2024-499770 days apartnet: stmmac: Fix zero-division error when disabling tc cbs22Monitor
- CVE-2024-4766312 days apartstaging: iio: frequency: ad9834: Validate frequency parameter value22Monitor
- CVE-2024-4766412 days apartspi: hisi-kunpeng: Add verification for the max_frequency provided by the firmware22Monitor
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)
CWE-369 · Divide By ZeroCVSS 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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.