ext4: update orig_path in ext4_find_extent()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.323, 5.10.227, 5.15.168, 6.1.113, 6.6.55, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: update orig_path in ext4_find_extent() In ext4_find_extent(), if the path is not big enough, we free it and set *orig_path to NULL. But after reallocating and successfully initializing the path, we don't update *orig_path, in which case the caller gets a valid path but a NULL ppath, and this may cause a NULL pointer dereference or a path memory leak. For example: ext4_split_extent path = *ppath = 2000 ext4_find_extent if (depth > path[0].p_maxdepth) kfree(path = 2000); *orig_path = path = NULL; path = kcalloc() = 3000 ext4_split_extent_at(*ppath = NULL) path = *ppath; ex = path[depth].p_ext; // NULL pointer dereference! ================================================================== BUG: kernel NULL pointer dereference, address: 0000000000000010 CPU: 6 UID: 0 PID: 576 Comm: fsstress Not tainted 6.11.0-rc2-dirty #847 RIP: 0010:ext4_split_extent_at+0x6d/0x560 Call Trace: <TASK> ext4_split_extent.isra.0+0xcb/0x1b0 ext4_ext_convert_to_initialized+0x168/0x6c0 ext4_ext_handle_unwritten_extents+0x325/0x4d0 ext4_ext_map_blocks+0x520/0xdb0 ext4_map_blocks+0x2b0/0x690 ext4_iomap_begin+0x20e/0x2c0 [...] ================================================================== Therefore, *orig_path is updated when the extent lookup succeeds, so that the caller can safely use path or *ppath.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 10809df84a4d868db61af621bae3658494165279 · fixed in ec0c0beb9b777cdd1edd7df9b36e0f3e67e2bdff; From 10809df84a4d868db61af621bae3658494165279 · fixed in 6766937d0327000ac1b87c97bbecdd28b0dd6599; From 10809df84a4d868db61af621bae3658494165279 · fixed in a9fcb1717d75061d3653ed69365c8d45331815cd; From 10809df84a4d868db61af621bae3658494165279 · fixed in 6801ed1298204d16a38571091e31178bfdc3c679; From 10809df84a4d868db61af621bae3658494165279 · fixed in f55ecc58d07a6c1f6d6d5b5af125c25f8da0bda2; From 10809df84a4d868db61af621bae3658494165279 · fixed in b63481b3a388ee2df9e295f97273226140422a42; From 10809df84a4d868db61af621bae3658494165279 · fixed in 11b230100d6801c014fab2afabc8bdea304c1b96; From 10809df84a4d868db61af621bae3658494165279 · fixed in 5b4b2dcace35f618fe361a87bae6f0d13af31bc1
- Linux Linux
3.18
- KernelLinux
From 3.18.0 · fixed in 4.19.323; From 4.20.0 · fixed in 5.10.227; From 5.11.0 · fixed in 5.15.168; From 5.16.0 · fixed in 6.1.113; From 6.2.0 · fixed in 6.6.55; From 6.7.0 · fixed in 6.10.14; From 6.11.0 · fixed in 6.11.3
References 8
git.kernel.org
- stable/c/ec0c0beb9b777cdd1edd7df9b36e0f3e67e2bdff
- stable/c/6766937d0327000ac1b87c97bbecdd28b0dd6599
- stable/c/a9fcb1717d75061d3653ed69365c8d45331815cd
- stable/c/6801ed1298204d16a38571091e31178bfdc3c679
- stable/c/f55ecc58d07a6c1f6d6d5b5af125c25f8da0bda2
- stable/c/b63481b3a388ee2df9e295f97273226140422a42
- stable/c/11b230100d6801c014fab2afabc8bdea304c1b96
- stable/c/5b4b2dcace35f618fe361a87bae6f0d13af31bc1