data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-43301 in the interactive tracker

CVE-2026-43301

media: chips-media: wave5: Fix PM runtime usage count underflow

EPSS 0.2%

Published 2026-05-08 (5 months ago) by the Linux kernel CNA. Subsystem drivers/media. Debian urgency: unimportant.

What to do, per Debian release

Debian's own status for CVE-2026-43301 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

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixievulnerable6.12.113-1No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication.
Debian 14forkyfixed6.19.6-1Update the kernel and reboot. Fixed in 6.19.6-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.19.6-1Update the kernel and reboot. Fixed in 6.19.6-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

Replace pm_runtime_put_sync() with pm_runtime_dont_use_autosuspend() in the remove path to properly pair with pm_runtime_use_autosuspend() from probe. This allows pm_runtime_disable() to handle reference count cleanup correctly regardless of current suspend state. The driver calls pm_runtime_put_sync() unconditionally in remove, but the device may already be suspended due to autosuspend configured in probe. When autosuspend has already suspended the device, the usage count is 0, and pm_runtime_put_sync() decrements it to -1. This causes the following warning on module unload: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 963 at kernel/kthread.c:1430 kthread_destroy_worker+0x84/0x98 ... vdec 30210000.video-codec: Runtime PM usage count underflow!

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/media/platform/chips-media/wave5/wave5-vpu.c

What this is
WAVE5 VPU CODEC DRIVERMAINTAINERS section matched on drivers/media/platform/chips-media/wave5/ · linux-media@vger.kernel.org · Maintained

Check it on the machine

grep -w CONFIG_VIDEO_WAVE_VPU /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.

Show whether Debian builds this, per release

Debian does not build this code in 3 releases. The build rule could not be established for 1 release, so nothing is claimed about those.

  • bookworm?
  • trixie, forky, sidn
?
not established - no Makefile entry for the affected file
n
not enabled on any flavour - this release does not build the code

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 switch
CONFIG_VIDEO_WAVE_VPU

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-05-08 (5 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.16%, higher than 4.8% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
drivers/media

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.86.18.163a278a55ead5
6.86.19.60bffda023179
6.87.09cf4452e824c

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-43301, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.