From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-93070: media: ipu6: Do not free aux device pdata after init
Date: Thu, 17 Sep 2026 17:15:49 +0100 [thread overview]
Message-ID: <2026091739-CVE-2026-93070-afca@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: ipu6: Do not free aux device pdata after init
ipu6_bus_initialize_device() stores the isys/psys pdata pointer in
struct ipu6_bus_device and initializes the auxiliary device. After that
point, error unwinding must drop the auxiliary device reference and let
ipu6_bus_release() free both the bus device and adev->pdata.
The isys and psys init paths already call put_device() when MMU
initialization fails, and ipu6_bus_add_device() calls
auxiliary_device_uninit() on auxiliary_device_add() failure. Both paths
therefore run the bus release callback. The extra kfree(pdata) in the
callers can release the same object a second time.
Remove the manual pdata frees after the auxiliary device has been
initialized.
This issue was found by a static analysis checker and confirmed by
manual source review.
The Linux kernel CVE team has assigned CVE-2026-93070 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit cb3117b074aefb0320d8d728a0a7f277a121adbd and fixed in 6.12.110 with commit faa1eb97f0e66bf122f44b62be6b323f86333e9f
Issue introduced in 6.10 with commit cb3117b074aefb0320d8d728a0a7f277a121adbd and fixed in 6.18.52 with commit 5323ed5a7bb2568191ec676b2035b0396105aa05
Issue introduced in 6.10 with commit cb3117b074aefb0320d8d728a0a7f277a121adbd and fixed in 7.2.6 with commit 7d102d1f0631807a491a140f67c9628dea85dfd2
Issue introduced in 6.10 with commit cb3117b074aefb0320d8d728a0a7f277a121adbd and fixed in 7.3-rc1 with commit 9be07216af4cfc4813e1a46ce26407d31ea845de
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-93070
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/media/pci/intel/ipu6/ipu6.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/faa1eb97f0e66bf122f44b62be6b323f86333e9f
https://git.kernel.org/stable/c/5323ed5a7bb2568191ec676b2035b0396105aa05
https://git.kernel.org/stable/c/7d102d1f0631807a491a140f67c9628dea85dfd2
https://git.kernel.org/stable/c/9be07216af4cfc4813e1a46ce26407d31ea845de
reply other threads:[~2026-09-17 16:35 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=2026091739-CVE-2026-93070-afca@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.