CVE-2026-64022: gpio: aggregator: remove the software node when deactivating the aggregator
Greg Kroah-Hartman <[email protected]>
| Newsgroups | org.kernel.vger.linux-cve-announce |
|---|---|
| Message-ID | <2026071902-CVE-2026-64022-1155@gregkh> |
From: Greg Kroah-Hartman <[email protected]> Description =========== In the Linux kernel, the following vulnerability has been resolved: gpio: aggregator: remove the software node when deactivating the aggregator The dynamic software node we create for the aggregator platform device when using configfs is leaked when the device is deactivated. Destroy it as the last step in the tear-down path. The Linux kernel CVE team has assigned CVE-2026-64022 to this issue. Affected and fixed versions =========================== Issue introduced in 6.16 with commit 86f162e73d2d81ef6d819c06a3b6c2fda77a79b8 and fixed in 6.18.34 with commit 3e657619cf7258cb53b1beaf0d02998297695cde Issue introduced in 6.16 with commit 86f162e73d2d81ef6d819c06a3b6c2fda77a79b8 and fixed in 7.0.11 with commit 9870ea9a4a25abef3e7af3445bfce2472528a546 Issue introduced in 6.16 with commit 86f162e73d2d81ef6d819c06a3b6c2fda77a79b8 and fixed in 7.1 with commit 61fef83f239ecace1cce716135762a2d9b7b1fc6 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-64022 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/gpio/gpio-aggregator.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/3e657619cf7258cb53b1beaf0d02998297695cde https://git.kernel.org/stable/c/9870ea9a4a25abef3e7af3445bfce2472528a546 https://git.kernel.org/stable/c/61fef83f239ecace1cce716135762a2d9b7b1fc6