CVE-2023-54069: ext4: fix BUG in ext4_mb_new_inode_pa() due to overflow
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 4.15, 4.20, 5.10.200.
Low priority for now. Upgrade to Linux Linux 4.15, 4.20, 5.10.200 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 BUG in ext4_mb_new_inode_pa() due to overflow When we calculate the end position of ext4_free_extent, this position may be exactly where ext4_lblk_t (i.e. uint) overflows. For example, if ac_g_ex.fe_logical is 4294965248 and ac_orig_goal_len is 2048, then the computed end is 0x100000000, which is 0. If ac->ac_o_ex.fe_logical is not the first case of adjusting the best extent, that is, new_bex_end > 0, the following BUG_ON will be triggered: ========================================================= kernel BUG at fs/ext4/mballoc.c:5116! invalid opcode: 0000 [#1] PREEMPT SMP PTI CPU: 3 PID: 673 Comm: xfs_io Tainted: G E 6.5.0-rc1+ #279 RIP: 0010:ext4_mb_new_inode_pa+0xc5/0x430 Call Trace: <TASK> ext4_mb_use_best_found+0x203/0x2f0 ext4_mb_try_best_found+0x163/0x240 ext4_mb_regular_allocator+0x158/0x1550 ext4_mb_new_blocks+0x86a/0xe10 ext4_ext_map_blocks+0xb0c/0x13a0 ext4_map_blocks+0x2cd/0x8f0 ext4_iomap_begin+0x27b/0x400 iomap_iter+0x222/0x3d0 __iomap_dio_rw+0x243/0xcb0 iomap_dio_rw+0x16/0x80 ========================================================= A simple reproducer demonstrating the problem: mkfs.ext4 -F /dev/sda -b 4096 100M mount /dev/sda /tmp/test fallocate -l1M /tmp/test/tmp fallocate -l10M /tmp/test/file fallocate -i -o 1M -l16777203M /tmp/test/file fsstress -d /tmp/test -l 0 -n 100000 -p 8 & sleep 10 && killall -9 fsstress rm -f /tmp/test/tmp xfs_io -c "open -ad /tmp/test/file" -c "pwrite -S 0xff 0 8192" We simply refactor the logic for adjusting the best extent by adding a temporary ext4_free_extent ex and use extent_logical_end() to avoid overflow, which also simplifies the code.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
—
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
- 46772ab99409cc72241227dd8f5295f358233fda, 25a60b4533268477920faaeebd99e7e69c0735cd, cec4ef62b36b04e0bc8905732adab091f4bc1cfd, 6.4affected
- 8659c5f4ffaacbe932849b98462c3d635b4eacea and later · before 83ecffd40c65844a73c2e93d7c841455786605acaffected · git
- fc7237e191b99f88e859316fab2b06c2c26c8344 and later · before 58fe961c606c446f5612f6897827b1cac42c2e89affected · git
- 613f6cde5ebb005a37fda117cdda7b4126170c13 and later · before f2c3a3aa6f11ad9878dbc3a067b0633e07b586c1affected · git
- 9d4430b7f862ce8835ca4e054b6916d15c8e0862 and later · before fcefddf3a151b2c416b20120c06bb1ba9ad676fbaffected · git
- 93cdf49f6eca5e23f6546b8f28457b2e6a6961d9 and later · before b7e9ec38b6a0beb5a49cd1e76be0a9a07c218e90affected · git
- 93cdf49f6eca5e23f6546b8f28457b2e6a6961d9 and later · before bc056e7163ac7db945366de219745cf94f32a3e6affected · git
- 5.4.244 and later · before 5.4.260affected · semver
- 5.10.181 and later · before 5.10.200affected · semver
- 5.15.113 and later · before 5.15.138affected · semver
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.64-1 | 6.1.64-1 |
| Debian:13 | linux | before 6.5.6-1 | 6.5.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54067Dec 24, 2025 · btrfs: fix race when deleting free space root from the dirty cow roots list31Monitor
- ← EarlierCVE-2023-54068Dec 24, 2025 · f2fs: compress: fix to call f2fs_wait_on_page_writeback() in f2fs_write_raw_pages()31Monitor
- Later →CVE-2023-54070Dec 24, 2025 · igb: clean up in all error paths when enabling SR-IOV0Monitor
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 | 4.15 | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 5.10.200 | Vendor (CNA) |
| Linux Linux | 5.15.138 | Vendor (CNA) |
| Linux Linux | 5.4.260 | Vendor (CNA) |
| Linux Linux | 58fe961c606c446f5612f6897827b1cac42c2e89 | Vendor (CNA) |
| Linux Linux | 6.1.61 | Vendor (CNA) |
| Linux Linux | 6.4 | Vendor (CNA) |
| Linux Linux | 83ecffd40c65844a73c2e93d7c841455786605ac | Vendor (CNA) |
| Linux Linux | b7e9ec38b6a0beb5a49cd1e76be0a9a07c218e90 | Vendor (CNA) |
| Linux Linux | bc056e7163ac7db945366de219745cf94f32a3e6 | Vendor (CNA) |
| Linux Linux | f2c3a3aa6f11ad9878dbc3a067b0633e07b586c1 | Vendor (CNA) |
| Linux Linux | fcefddf3a151b2c416b20120c06bb1ba9ad676fb | Vendor (CNA) |
| debian:linux | 6.1.64-1 · Debian:12 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (5 more)Show less
- git.kernel.org/stable/c/83ecffd40c65844a73c2e93d7c841455786605ac
- git.kernel.org/stable/c/b7e9ec38b6a0beb5a49cd1e76be0a9a07c218e90
- git.kernel.org/stable/c/bc056e7163ac7db945366de219745cf94f32a3e6
- git.kernel.org/stable/c/f2c3a3aa6f11ad9878dbc3a067b0633e07b586c1
- git.kernel.org/stable/c/fcefddf3a151b2c416b20120c06bb1ba9ad676fb
Vendor advisories and official records. Exploit/PoC links are deliberately left out.