From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89886: media: intel/ipu6: fix async notifier cleanup leak on parse error
Date: Wed, 16 Sep 2026 11:30:16 +0100 [thread overview]
Message-ID: <2026091633-CVE-2026-89886-4487@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: intel/ipu6: fix async notifier cleanup leak on parse error
isys_notifier_init() calls v4l2_async_nf_init() and then adds fwnode
remote subdevs in a loop with v4l2_async_nf_add_fwnode_remote(). If an
endpoint parse or add fails partway through the loop, it jumps to
err_parse and returns without calling v4l2_async_nf_cleanup(), leaking
every v4l2_async_connection already added to the notifier's waiting
list.
The register-failure path just below already cleans up correctly, and
the caller only tears the notifier down (isys_notifier_cleanup()) once
isys_notifier_init() has returned success. Clean up the notifier on the
parse error path too.
The Linux kernel CVE team has assigned CVE-2026-89886 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit f50c4ca0a82003b8a542c3332fd292cf1bc355a2 and fixed in 6.12.110 with commit dd5943aedbe4d7eb46158cb35078257733ac48b6
Issue introduced in 6.10 with commit f50c4ca0a82003b8a542c3332fd292cf1bc355a2 and fixed in 6.18.51 with commit 27b7997be552ee37b3e01beacfeb4131f1bebb5f
Issue introduced in 6.10 with commit f50c4ca0a82003b8a542c3332fd292cf1bc355a2 and fixed in 7.2.5 with commit eee6069e4e9511e814a33a75e403f7e863f70394
Issue introduced in 6.10 with commit f50c4ca0a82003b8a542c3332fd292cf1bc355a2 and fixed in 7.3-rc1 with commit abb1f808ceab5a3275f8a6b4e37cff17f9f781c1
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-89886
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-isys.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/dd5943aedbe4d7eb46158cb35078257733ac48b6
https://git.kernel.org/stable/c/27b7997be552ee37b3e01beacfeb4131f1bebb5f
https://git.kernel.org/stable/c/eee6069e4e9511e814a33a75e403f7e863f70394
https://git.kernel.org/stable/c/abb1f808ceab5a3275f8a6b4e37cff17f9f781c1
reply other threads:[~2026-09-16 10:39 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=2026091633-CVE-2026-89886-4487@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.