interconnect: Fix use after free in icc_get() and of_icc_get_by_index()
- 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 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 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
Summary
In the Linux kernel, the following vulnerability has been resolved: interconnect: Fix use after free in icc_get() and of_icc_get_by_index() In of_icc_get_by_index() and icc_get(), if the dynamic allocation for path->name fails via kasprintf(), the error handling path directly calls kfree(path) to free the path object and returns an error. However, prior to this point, path_find() calls path_init(), which already links the path's requests into the req_list of the respective interconnect nodes via hlist_add_head(). Directly invoking kfree(path) leaves dangling pointers in the hlist. A subsequent call to icc_get() or icc_set_bw() will traverse or modify these corrupted lists, triggering a slab use afterfree. KASAN report showing the vulnerability when reproducing via debugfs: BUG: KASAN: slab-use-after-free in path_find+0x6f8/0xcfc Write of size 8 at addr fff000000d43f748 by task sh/1 ... Call trace: kasan_report+0xac/0xfc path_find+0x6f8/0xcfc icc_get+0x148/0x380 icc_get_set+0xf8/0x2d0 ... Freed by task 1: kfree+0x1a0/0x4a4 icc_get+0x2cc/0x380 icc_get_set+0xf8/0x2d0 Fix this by replacing kfree(path) with the proper teardown function, icc_put(path), which safely removes the requests from the req_list using hlist_del() and drops the provider usage references before freeing the memory. Additionally, in icc_get(), ensure that the icc_lock mutex is released prior to calling icc_put(path) to avoid a deadlock, as icc_put() internally acquires the same lock.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 3791163602f7140011a8dc1691cfe6ec0cb1ef07 · fixed in 03c3af594dea9196cf6ca70d914b42aa8c873c35; From 3791163602f7140011a8dc1691cfe6ec0cb1ef07 · fixed in d4d73decdb9a44a248b1cbd04ed6f334df544d9c; From 3791163602f7140011a8dc1691cfe6ec0cb1ef07 · fixed in 9a671125d4228357e5b929733c4593d27a273749; From 3791163602f7140011a8dc1691cfe6ec0cb1ef07 · fixed in fedea72e8f312fe7d0c6cb19353e61d2d5643b11; From 3791163602f7140011a8dc1691cfe6ec0cb1ef07 · fixed in a4e9aa7907ade87d1d96853d14e05dcf682f8363; From 3791163602f7140011a8dc1691cfe6ec0cb1ef07 · fixed in db8147c5d5ad2cfa21c2be566f95981b41b05de6; From 3791163602f7140011a8dc1691cfe6ec0cb1ef07 · fixed in d715d19cfcfe99f361adb05cefc143a95d400b87; From 3791163602f7140011a8dc1691cfe6ec0cb1ef07 · fixed in 25c7e242aca084fdc1098248194032317dca625d
- Linux Linux
5.6
- KernelLinux
From 5.6.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4
References 8
git.kernel.org
- stable/c/03c3af594dea9196cf6ca70d914b42aa8c873c35
- stable/c/d4d73decdb9a44a248b1cbd04ed6f334df544d9c
- stable/c/9a671125d4228357e5b929733c4593d27a273749
- stable/c/fedea72e8f312fe7d0c6cb19353e61d2d5643b11
- stable/c/a4e9aa7907ade87d1d96853d14e05dcf682f8363
- stable/c/db8147c5d5ad2cfa21c2be566f95981b41b05de6
- stable/c/d715d19cfcfe99f361adb05cefc143a95d400b87
- stable/c/25c7e242aca084fdc1098248194032317dca625d