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… (CVE-2026-81008)
A use-after-free vulnerability in the Linux kernel interconnect subsystem was fixed. The issue occurs when dynamic allocation for a path name fails, leading to improper freeing of the path object and leaving dangling pointers in internal lists. This can cause kernel memory corruption and potential instability. The fix replaces a direct free call with a proper teardown function that safely removes references and avoids deadlocks.
AI Analysis
Technical Summary
The Linux kernel interconnect subsystem had a use-after-free vulnerability in the functions icc_get() and of_icc_get_by_index(). When dynamic allocation of path->name via kasprintf() fails, the error path incorrectly calls kfree(path) directly, despite the path's requests already being linked into interconnect nodes' req_list. This leaves dangling pointers in the hlist, causing slab use-after-free errors when subsequent calls traverse or modify these corrupted lists. The fix replaces kfree(path) with icc_put(path), which safely removes requests from the req_list and drops provider usage references before freeing memory. Additionally, icc_lock mutex is released before calling icc_put(path) to prevent deadlocks.
Potential Impact
This vulnerability can lead to kernel memory corruption due to use-after-free conditions, potentially causing system crashes or instability. There is no indication of known exploits in the wild. The impact is limited to kernel stability and security, with no direct evidence of privilege escalation or remote code execution.
Mitigation Recommendations
A fix is available and has been applied in the Linux kernel source. The vulnerability is resolved by replacing the improper kfree(path) call with the proper icc_put(path) teardown function and ensuring correct mutex handling to avoid deadlocks. Users should update to the fixed kernel version once available. No additional mitigation is required beyond applying the official fix.
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… (CVE-2026-81008)
Description
A use-after-free vulnerability in the Linux kernel interconnect subsystem was fixed. The issue occurs when dynamic allocation for a path name fails, leading to improper freeing of the path object and leaving dangling pointers in internal lists. This can cause kernel memory corruption and potential instability. The fix replaces a direct free call with a proper teardown function that safely removes references and avoids deadlocks.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel interconnect subsystem had a use-after-free vulnerability in the functions icc_get() and of_icc_get_by_index(). When dynamic allocation of path->name via kasprintf() fails, the error path incorrectly calls kfree(path) directly, despite the path's requests already being linked into interconnect nodes' req_list. This leaves dangling pointers in the hlist, causing slab use-after-free errors when subsequent calls traverse or modify these corrupted lists. The fix replaces kfree(path) with icc_put(path), which safely removes requests from the req_list and drops provider usage references before freeing memory. Additionally, icc_lock mutex is released before calling icc_put(path) to prevent deadlocks.
Potential Impact
This vulnerability can lead to kernel memory corruption due to use-after-free conditions, potentially causing system crashes or instability. There is no indication of known exploits in the wild. The impact is limited to kernel stability and security, with no direct evidence of privilege escalation or remote code execution.
Mitigation Recommendations
A fix is available and has been applied in the Linux kernel source. The vulnerability is resolved by replacing the improper kfree(path) call with the proper icc_put(path) teardown function and ensuring correct mutex handling to avoid deadlocks. Users should update to the fixed kernel version once available. No additional mitigation is required beyond applying the official fix.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3v62-228g-v2c5
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-81008"]
Threat ID: 6aa4a02855bf5e2cf5a86b1d
Added to database: 09/12/2026, 00:43:20 UTC
Last enriched: 09/12/2026, 01:20:47 UTC
Last updated: 09/12/2026, 01:20:47 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.