CVE-2026-81008
interconnect: Fix use after free in icc_get() and of_icc_get_by_index()
Reported by linux · Published September 11, 2026
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.
EPSS 0.16% · 5.7th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | db8147c5d5ad2cfa21c2be566f95981b41b05de6, d715d19cfcfe99f361adb05cefc143a95d400b87, a4e9aa7907ade87d1d96853d14e05dcf682f8363, 25c7e242aca084fdc1098248194032317dca625d |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 3791163602f7140011a8dc1691cfe6ec0cb1ef07, 3791163602f7140011a8dc1691cfe6ec0cb1ef07, 3791163602f7140011a8dc1691cfe6ec0cb1ef07 |
| Linux | Linux | 5.6, 0, 5.10.270 |
| Linux | Linux | 7.3, 3791163602f7140011a8dc1691cfe6ec0cb1ef07, 3791163602f7140011a8dc1691cfe6ec0cb1ef07 |
| linux | linux_kernel | 5.6, 5.6, 5.6 |
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (10 in total, the first dated here)
- Sep 12, 2026 Coalition ESS Score
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-81008
vulnetix vdb fixes CVE-2026-81008
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-81008/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart