Look up another CVE · open CVE-2026-89522 in the interactive tracker
CVE-2026-89522
media: staging/ipu7: fix async notifier UAF on probe error path
Published 2026-09-11 (37 days ago) by the Linux kernel CNA. Subsystem drivers/staging. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-89522 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | not affected | 6.12.113-1 | Nothing to do. trixie never shipped the vulnerable code. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
isys_register_devices() registers the V4L2 async notifier via isys_notifier_init(). If a subsequent probe step such as isys_fw_log_init() fails, isys_probe() jumps to the out_cleanup label which only calls isys_unregister_devices(). That helper tears down the video devices, subdevices, V4L2 device and media device, but never unregisters or cleans up the async notifier. As a result the notifier stays chained in the global notifier_list while the enclosing struct ipu7_isys is freed by devres, leading to list corruption and a use-after-free the next time the list is walked. The remove path already does the right thing by calling isys_notifier_cleanup() before isys_unregister_devices(). Mirror that on the probe error path so the notifier is unregistered and cleaned up before the device is torn down.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/staging/media/ipu7/ipu7-isys.c
- What this is
- INTEL IPU7 INPUT SYSTEM DRIVERMAINTAINERS section matched on drivers/staging/media/ipu7/ · linux-media@vger.kernel.org · Maintained
- Kernel module
- intel_ipu7_isys
Check it on the machine
grep -wE 'CONFIG_STAGING|CONFIG_VIDEO_INTEL_IPU7' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w intel_ipu7_isysPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 2 releases, so nothing is claimed about those.
- bookworm, trixie?
- forky, sidMnot built on amd64/cloud-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_STAGING, CONFIG_VIDEO_INTEL_IPU7
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-11 (37 days ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.17%, higher than 5.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/staging
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.17 | 6.18.50 | 2a8dd9fd12f3 |
| 6.17 | 7.2.4 | 323c411fb631 |
| 6.17 | 7.3 | d7f48aa7d60c |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The flaw is in isys_probe() of the Intel IPU7 ISYS auxiliary driver (PCI IDs 0x645d/0xb05d on Meteor Lake/Arrow Lake/Lunar Lake laptops). It is reached only via local driver bind of the onboard MIPI camera ISP, not via network packets, Bluetooth, or USB attachment.
- AC:LAttack complexity, low
- The missing isys_notifier_cleanup() on the out_cleanup path is deterministic. A local attacker can force the subsequent 2 MiB FW_LOG_BUF_SIZE kzalloc in isys_fw_log_init() to fail under memory pressure, and the UAF is then hit the next time notifier_list is walked, with no race the attacker must win.
- PR:LPrivileges required, low
- After probe failure leaves the notifier on the global notifier_list, ACPI camera sensors typical of IPU7 laptops (ov02c10, ov08x40, and similar) call v4l2_async_register_subdev_sensor() and walk that list without capabilities. Per CNA guidance, Low is used when probe/bind privilege gating is ambiguous.
- UI:NUser interaction, none
- No victim action such as opening /dev/video*, mounting a filesystem, or plugging a device is required. The dangling notifier is planted on the probe error path and consumed automatically when a sensor or other V4L2 async client registers.
- S:UScope, unchanged
- Impact is host-kernel slab use-after-free and list corruption inside the IPU7/V4L2 async core. This is standard kernel privilege-escalation territory and does not cross a VM, IOMMU, or sandbox security boundary.
- C:HConfidentiality impact, high
- The notifier is embedded in struct ipu7_isys, which devres frees while it remains linked on notifier_list. A later walk reads freed notifier fields and ops; per kernel CNA UAF guidance that reuse primitive enables arbitrary kernel memory disclosure.
- I:HIntegrity impact, high
- Walking or unlinking the dangling notifier_entry corrupts kernel lists, and a reclaimed object can redirect notifier->ops (bound/complete) to attacker-controlled function pointers, yielding an arbitrary-write and control-flow hijack primitive.
- A:HAvailability impact, high
- The next notifier_list walk or bound callback on the freed ipu7_isys object causes a kernel oops or panic, and use-after-free heap corruption inherently denies availability even without a full exploit.