CVE-2022-49708: ext4: fix bug_on ext4_mb_use_inode_pa
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.28% (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 3.11, 3.13, 3.17.
Low priority for now. Upgrade to Linux Linux 3.11, 3.13, 3.17 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 ext4_mb_use_inode_pa Hulk Robot reported a BUG_ON: ================================================================== kernel BUG at fs/ext4/mballoc.c:3211! [...] RIP: 0010:ext4_mb_mark_diskspace_used.cold+0x85/0x136f [...] Call Trace: ext4_mb_new_blocks+0x9df/0x5d30 ext4_ext_map_blocks+0x1803/0x4d80 ext4_map_blocks+0x3a4/0x1a10 ext4_writepages+0x126d/0x2c30 do_writepages+0x7f/0x1b0 __filemap_fdatawrite_range+0x285/0x3b0 file_write_and_wait_range+0xb1/0x140 ext4_sync_file+0x1aa/0xca0 vfs_fsync_range+0xfb/0x260 do_fsync+0x48/0xa0 [...] ================================================================== Above issue may happen as follows: ------------------------------------- do_fsync vfs_fsync_range ext4_sync_file file_write_and_wait_range __filemap_fdatawrite_range do_writepages ext4_writepages mpage_map_and_submit_extent mpage_map_one_extent ext4_map_blocks ext4_mb_new_blocks ext4_mb_normalize_request >>> start + size <= ac->ac_o_ex.fe_logical ext4_mb_regular_allocator ext4_mb_simple_scan_group ext4_mb_use_best_found ext4_mb_new_preallocation ext4_mb_new_inode_pa ext4_mb_use_inode_pa >>> set ac->ac_b_ex.fe_len <= 0 ext4_mb_mark_diskspace_used >>> BUG_ON(ac->ac_b_ex.fe_len <= 0); we can easily reproduce this problem with the following commands: `fallocate -l100M disk` `mkfs.ext4 -b 1024 -g 256 disk` `mount disk /mnt` `fsstress -d /mnt -l 0 -n 1000 -p 1` The size must be smaller than or equal to EXT4_BLOCKS_PER_GROUP. Therefore, "start + size <= ac->ac_o_ex.fe_logical" may occur when the size is truncated. So start should be the start position of the group where ac_o_ex.fe_logical is located after alignment. In addition, when the value of fe_logical or EXT4_BLOCKS_PER_GROUP is very large, the value calculated by start_off is more accurate.
- 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 kernel3.2.89 and later · before 3.3
- linux linux kernel3.10.107 and later · before 3.11
- linux linux kernel3.12.72 and later · before 3.13
- linux linux kernel3.16.44 and later · before 3.17
- linux linux kernel4.1.40 and later · before 4.2
- linux linux kernel4.4.53 and later · before 4.5
- linux linux kernel4.9.14 and later · before 4.9.320
- linux linux kernel4.10.2 and later · before 4.14.285
- linux linux kernel4.15 and later · before 4.19.249
- linux linux kernel4.20 and later · before 5.4.200
- linux linux kernel5.5 and later · before 5.10.124
- linux linux kernel5.11 and later · before 5.15.49
- linux linux kernel5.16 and later · before 5.18.6
- linux linux kernel5.19
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
- f213db429b883a2d5403de0b1ce92fb7d7ee979e, 98f58e05231f835dfb09359e3b5e3a886fe8f189, c1664e9bcf6291c0ceb8599f57c8cf493526abe6, 37cf4ab1ba60c30ca9fd0fe3b9993b24cb87886a, 75f37dab088eb84ff25a49e59371f01ea3f44aa7, 8774c73cf6963310395823ed7077ea12943ea0f3, c4fbdc0124799f1772f4d886b7f2e1a6f881d195, 4.11affected
- fc6c2da174edd7a7b760b12c60d432d300e05cca and later · before 6880fb2e64331b9fdc85d3f32b1d7e81ad8703f1affected · git
- cd648b8a8fd5071d232242d5ee7ee3c0815776af and later · before a37c1359714da42517dd19d36fc3c4d17edba832affected · git
- cd648b8a8fd5071d232242d5ee7ee3c0815776af and later · before 5707d721d1819db57dba57b1d4623034fcb32047affected · git
- cd648b8a8fd5071d232242d5ee7ee3c0815776af and later · before a6b31616e5afe1d3972cb0682a373e50597faf5caffected · git
- cd648b8a8fd5071d232242d5ee7ee3c0815776af and later · before 6fdaf31ad5f3d3afab744dfd9a8b0d9142aa881faffected · git
- cd648b8a8fd5071d232242d5ee7ee3c0815776af and later · before 90f0f9d45dff0128c0fca0d2358c4153b024afa6affected · git
- cd648b8a8fd5071d232242d5ee7ee3c0815776af and later · before 887a3e9ad4b8309a2266bce7ae749b2bf1f7a687affected · git
- cd648b8a8fd5071d232242d5ee7ee3c0815776af and later · before a08f789d2ab5242c07e716baf9a835725046be89affected · git
- 4.9.14 and later · before 4.9.320affected · 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 5.18.14-1 | 5.18.14-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-2022-49706Feb 26, 2025 · zonefs: fix zonefs_iomap_begin() for reads28Monitor
- ← EarlierCVE-2022-49707Feb 26, 2025 · ext4: add reserved GDT blocks check22Monitor
- Later →CVE-2022-49709Feb 26, 2025 · cfi: Fix __cfi_slowpath_diag RCU usage with cpuidle22Monitor
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 | 3.11 | Vendor (CNA) |
| Linux Linux | 3.13 | Vendor (CNA) |
| Linux Linux | 3.17 | Vendor (CNA) |
| Linux Linux | 3.3 | Vendor (CNA) |
| Linux Linux | 4.11 | Vendor (CNA) |
| Linux Linux | 4.2 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 4.9.320 | Vendor (CNA) |
| Linux Linux | 5707d721d1819db57dba57b1d4623034fcb32047 | Vendor (CNA) |
| Linux Linux | 6880fb2e64331b9fdc85d3f32b1d7e81ad8703f1 | Vendor (CNA) |
| Linux Linux | 6fdaf31ad5f3d3afab744dfd9a8b0d9142aa881f | Vendor (CNA) |
| Linux Linux | 887a3e9ad4b8309a2266bce7ae749b2bf1f7a687 | Vendor (CNA) |
| Linux Linux | 90f0f9d45dff0128c0fca0d2358c4153b024afa6 | Vendor (CNA) |
| Linux Linux | a08f789d2ab5242c07e716baf9a835725046be89 | Vendor (CNA) |
| Linux Linux | a37c1359714da42517dd19d36fc3c4d17edba832 | Vendor (CNA) |
| Linux Linux | a6b31616e5afe1d3972cb0682a373e50597faf5c | Vendor (CNA) |
| debian:linux | 5.18.14-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 (7 more)Show less
- git.kernel.org/stable/c/6880fb2e64331b9fdc85d3f32b1d7e81ad8703f1
- git.kernel.org/stable/c/6fdaf31ad5f3d3afab744dfd9a8b0d9142aa881f
- git.kernel.org/stable/c/887a3e9ad4b8309a2266bce7ae749b2bf1f7a687
- git.kernel.org/stable/c/90f0f9d45dff0128c0fca0d2358c4153b024afa6
- git.kernel.org/stable/c/a08f789d2ab5242c07e716baf9a835725046be89
- git.kernel.org/stable/c/a37c1359714da42517dd19d36fc3c4d17edba832
- git.kernel.org/stable/c/a6b31616e5afe1d3972cb0682a373e50597faf5c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.