From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72077: Input: ims-pcu - fix firmware leak in async update
Date: Sat, 15 Aug 2026 15:02:36 +0900 [thread overview]
Message-ID: <2026081520-CVE-2026-72077-6a03@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Input: ims-pcu - fix firmware leak in async update
The firmware object was not being released if validation failed.
Use __free(firmware) to ensure the firmware is always released.
The Linux kernel CVE team has assigned CVE-2026-72077 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.6.148 with commit a5dd47ea3904dedb1ae7a5fe0e6b44a458f0c5ec
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.12.97 with commit 1f7bdfbe791aacad77db87f044e78ef60a93ae0d
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.18.40 with commit 99c428d7ef644d3e394f3072f905040c16dab18d
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 7.1.5 with commit 47a9889a9325b87698b6d6eaf3187a9af6e4773d
Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 7.2-rc1 with commit d48795b5cd6828d36b707e8d62fc9e5c90e004ab
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-72077
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/a5dd47ea3904dedb1ae7a5fe0e6b44a458f0c5ec
https://git.kernel.org/stable/c/1f7bdfbe791aacad77db87f044e78ef60a93ae0d
https://git.kernel.org/stable/c/99c428d7ef644d3e394f3072f905040c16dab18d
https://git.kernel.org/stable/c/47a9889a9325b87698b6d6eaf3187a9af6e4773d
https://git.kernel.org/stable/c/d48795b5cd6828d36b707e8d62fc9e5c90e004ab
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-72077-6a03@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.