ext4: fix bug_on in ext4_writepages
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.29% (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 013f12bdedb96816aaa27ee04349f4433d361f52, 18a759f7f99f0b65a08ff5b7e745fc405a42bde4, 19918ec7717d87d5ab825884a46b26b21375d7ce.
Low priority for now. Upgrade to Linux Linux 013f12bdedb96816aaa27ee04349f4433d361f52, 18a759f7f99f0b65a08ff5b7e745fc405a42bde4, 19918ec7717d87d5ab825884a46b26b21375d7ce 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_on in ext4_writepages we got issue as follows: EXT4-fs error (device loop0): ext4_mb_generate_buddy:1141: group 0, block bitmap and bg descriptor inconsistent: 25 vs 31513 free cls ------------[ cut here ]------------ kernel BUG at fs/ext4/inode.c:2708! invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 2 PID: 2147 Comm: rep Not tainted 5.18.0-rc2-next-20220413+ #155 RIP: 0010:ext4_writepages+0x1977/0x1c10 RSP: 0018:ffff88811d3e7880 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffff88811c098000 RDX: 0000000000000000 RSI: ffff88811c098000 RDI: 0000000000000002 RBP: ffff888128140f50 R08: ffffffffb1ff6387 R09: 0000000000000000 R10: 0000000000000007 R11: ffffed10250281ea R12: 0000000000000001 R13: 00000000000000a4 R14: ffff88811d3e7bb8 R15: ffff888128141028 FS: 00007f443aed9740(0000) GS:ffff8883aef00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000020007200 CR3: 000000011c2a4000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> do_writepages+0x130/0x3a0 filemap_fdatawrite_wbc+0x83/0xa0 filemap_flush+0xab/0xe0 ext4_alloc_da_blocks+0x51/0x120 __ext4_ioctl+0x1534/0x3210 __x64_sys_ioctl+0x12c/0x170 do_syscall_64+0x3b/0x90 It may happen as follows: 1. write inline_data inode vfs_write new_sync_write ext4_file_write_iter ext4_buffered_write_iter generic_perform_write ext4_da_write_begin ext4_da_write_inline_data_begin -> If inline data size too small will allocate block to write, then mapping will has dirty page ext4_da_convert_inline_data_to_extent ->clear EXT4_STATE_MAY_INLINE_DATA 2. fallocate do_vfs_ioctl ioctl_preallocate vfs_fallocate ext4_fallocate ext4_convert_inline_data ext4_convert_inline_data_nolock ext4_map_blocks -> fail will goto restore data ext4_restore_inline_data ext4_create_inline_data ext4_write_inline_data ext4_set_inode_state -> set inode EXT4_STATE_MAY_INLINE_DATA 3. writepages __ext4_ioctl ext4_alloc_da_blocks filemap_flush filemap_fdatawrite_wbc do_writepages ext4_writepages if (ext4_has_inline_data(inode)) BUG_ON(ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA)) The root cause of this issue is we destory inline data until call ext4_writepages under delay allocation mode. But there maybe already convert from inline to extent. To solve this issue, we call filemap_flush first..
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-617
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%
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 kernelbefore 4.9.318
- linux linux kernel4.10 and later · before 4.14.283
- linux linux kernel4.15 and later · before 4.19.247
- linux linux kernel4.20 and later · before 5.4.198
- linux linux kernel5.5 and later · before 5.10.121
- linux linux kernel5.11 and later · before 5.15.46
- linux linux kernel5.16 and later · before 5.17.14
- linux linux kernel5.18 and later · before 5.18.3
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.8affected
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 19918ec7717d87d5ab825884a46b26b21375d7ceaffected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before b2b78f5bf2d453dda3903955efee059260787a42affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before de1732b5c1693ad489c5d254f124f67cb775f37daffected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 73fd5b19285197078ee8a2e651d75d5b094a4de9affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 1b061af037646c9cdb0afd8a8d2f1e1c06285866affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 18a759f7f99f0b65a08ff5b7e745fc405a42bde4affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 1cde35417edc0370fb0179a4e38b78a15350a8d0affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before 013f12bdedb96816aaa27ee04349f4433d361f52affected · git
- 3c47d54170b6a678875566b1b8d6dcf57904e49b and later · before ef09ed5d37b84d18562b30cf7253e57062d0db05affected · 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 5.18.5-1 | 5.18.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- 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
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 013f12bdedb96816aaa27ee04349f4433d361f52 | Vendor (CNA) |
| Linux Linux | 18a759f7f99f0b65a08ff5b7e745fc405a42bde4 | Vendor (CNA) |
| Linux Linux | 19918ec7717d87d5ab825884a46b26b21375d7ce | Vendor (CNA) |
| Linux Linux | 1b061af037646c9cdb0afd8a8d2f1e1c06285866 | Vendor (CNA) |
| Linux Linux | 1cde35417edc0370fb0179a4e38b78a15350a8d0 | Vendor (CNA) |
| Linux Linux | 73fd5b19285197078ee8a2e651d75d5b094a4de9 | Vendor (CNA) |
| Linux Linux | b2b78f5bf2d453dda3903955efee059260787a42 | Vendor (CNA) |
| Linux Linux | de1732b5c1693ad489c5d254f124f67cb775f37d | Vendor (CNA) |
| Linux Linux | ef09ed5d37b84d18562b30cf7253e57062d0db05 | Vendor (CNA) |
| debian:linux | 5.18.5-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.
- CVE-2026-31739429 days apartcrypto: tegra - Add missing CRYPTO_ALG_ASYNC35Monitor
- CVE-2026-52952483 days apartiommu: Fix WARN_ON in __iommu_group_set_domain_nofail() due to reset35Monitor
- CVE-2025-39803201 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()31Monitor
- CVE-2023-52621337 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers31Monitor
- CVE-2026-31398401 days apartmm/rmap: fix incorrect pte restoration for lazyfree folios31Monitor
- CVE-2026-46117456 days apartRDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()31Monitor
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-617 · Reachable AssertionCVSS 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 (8 more)Show less
- git.kernel.org/stable/c/18a759f7f99f0b65a08ff5b7e745fc405a42bde4
- git.kernel.org/stable/c/19918ec7717d87d5ab825884a46b26b21375d7ce
- git.kernel.org/stable/c/1b061af037646c9cdb0afd8a8d2f1e1c06285866
- git.kernel.org/stable/c/1cde35417edc0370fb0179a4e38b78a15350a8d0
- git.kernel.org/stable/c/73fd5b19285197078ee8a2e651d75d5b094a4de9
- git.kernel.org/stable/c/b2b78f5bf2d453dda3903955efee059260787a42
- git.kernel.org/stable/c/de1732b5c1693ad489c5d254f124f67cb775f37d
- git.kernel.org/stable/c/ef09ed5d37b84d18562b30cf7253e57062d0db05
Vendor advisories and official records. Exploit/PoC links are deliberately left out.