From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72079: Input: ims-pcu - fix use-after-free and double-free in disconnect
Date: Sat, 15 Aug 2026 15:02:38 +0900 [thread overview]
Message-ID: <2026081520-CVE-2026-72079-0a52@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Input: ims-pcu - fix use-after-free and double-free in disconnect
ims_pcu_disconnect() only intended to perform cleanup when the primary
(control) interface is unbound. However, it currently relies on the
interface class to distinguish between control and data interfaces.
A malicious device could present a data interface with the same class
as the control interface, leading to premature cleanup and potential
use-after-free or double-free.
Switch to verifying that the interface being disconnected is indeed
the control interface.
The Linux kernel CVE team has assigned CVE-2026-72079 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 5.10.261 with commit 315f269ea04bc1477ab9bf351e939623d12a1621
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 5.15.212 with commit 293388e42e5c0865204de6f36bfb8662156fce3b
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.1.178 with commit 921abbb33887052e46b1b77299f87a3c741dc580
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.6.145 with commit 6a6c373e6a82eddc522342c8a8db7072c65f2b56
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.12.97 with commit a4b3f4d42fbf58f06f0d49e37a9d0d9392eca338
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.18.40 with commit 6aacc18004b1a915ccb8a829d30279a37988066e
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 7.1.5 with commit bf0b58ba489d0bdaa18c7dd8beeaeb954dd7dbb7
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 7.2-rc1 with commit 462a999917755a3bf77448dfd64307963cf0a9f0
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-72079
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/input/misc/ims-pcu.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/315f269ea04bc1477ab9bf351e939623d12a1621
https://git.kernel.org/stable/c/293388e42e5c0865204de6f36bfb8662156fce3b
https://git.kernel.org/stable/c/921abbb33887052e46b1b77299f87a3c741dc580
https://git.kernel.org/stable/c/6a6c373e6a82eddc522342c8a8db7072c65f2b56
https://git.kernel.org/stable/c/a4b3f4d42fbf58f06f0d49e37a9d0d9392eca338
https://git.kernel.org/stable/c/6aacc18004b1a915ccb8a829d30279a37988066e
https://git.kernel.org/stable/c/bf0b58ba489d0bdaa18c7dd8beeaeb954dd7dbb7
https://git.kernel.org/stable/c/462a999917755a3bf77448dfd64307963cf0a9f0
reply other threads:[~2026-08-15 6:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081520-CVE-2026-72079-0a52@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.