ubi: Fix use-after-free when volume resizing failed
- 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.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.100, 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: total
Summary
In the Linux kernel, the following vulnerability has been resolved: ubi: Fix use-after-free when volume resizing failed There is an use-after-free problem reported by KASAN: ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi] ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record() returns an error in ubi_resize_volume(), "new_eba_tbl" will be freed on error handing path, but it is holded by "vol->eba_tbl" in ubi_eba_replace_table(). It means that the liftcycle of "vol->eba_tbl" and "vol" are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by not freeing "new_eba_tbl" after it replaced in ubi_eba_replace_table(), while will be freed in next volume resizing.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 801c135ce73d5df1caf3eca35b66a10824ae0707 · fixed in bf9875aa7f7d624a8c084425b14bf7e5907ebc30; From 801c135ce73d5df1caf3eca35b66a10824ae0707 · fixed in bf795ebbb9995e2fe7945de71177f01c2f1215dc; From 801c135ce73d5df1caf3eca35b66a10824ae0707 · fixed in 9c8be1f165baee53b5a36ea0b3c9281d403a1d0b; From 801c135ce73d5df1caf3eca35b66a10824ae0707 · fixed in 35f8d4064e54c18424db2997059d4c0b1d13d093; From 801c135ce73d5df1caf3eca35b66a10824ae0707 · fixed in 53818746e549e61841428892a8d94344494be797; From 801c135ce73d5df1caf3eca35b66a10824ae0707 · fixed in b0c951742348d216f094d16ed4f70ae73db881c0; From 801c135ce73d5df1caf3eca35b66a10824ae0707 · fixed in 3d6378f7056ac7350338f941001162a8f660853c; From 801c135ce73d5df1caf3eca35b66a10824ae0707 · fixed in 9af31d6ec1a4be4caab2550096c6bd2ba8fba472
- Linux Linux
2.6.22
- KernelLinux
From 2.6.22 · fixed in 4.14.308; From 4.15.0 · fixed in 4.19.276; From 4.20.0 · fixed in 5.4.235; From 5.5.0 · fixed in 5.10.173; From 5.11.0 · fixed in 5.15.100; From 5.16.0 · fixed in 6.1.18; From 6.2.0 · fixed in 6.2.5
References 8
git.kernel.org
- stable/c/bf9875aa7f7d624a8c084425b14bf7e5907ebc30
- stable/c/bf795ebbb9995e2fe7945de71177f01c2f1215dc
- stable/c/9c8be1f165baee53b5a36ea0b3c9281d403a1d0b
- stable/c/35f8d4064e54c18424db2997059d4c0b1d13d093
- stable/c/53818746e549e61841428892a8d94344494be797
- stable/c/b0c951742348d216f094d16ed4f70ae73db881c0
- stable/c/3d6378f7056ac7350338f941001162a8f660853c
- stable/c/9af31d6ec1a4be4caab2550096c6bd2ba8fba472