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

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

CVE-2026-74329

watchdog: unregister PM notifier on watchdog unregister

EPSS 0.2%

Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem drivers/watchdog. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-74329 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 12bookwormfixed6.1.180-1Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixed6.12.100-1Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.1.5-1Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.5-1Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

watchdog_register_device() registers wdd->pm_nb when WDOG_NO_PING_ON_SUSPEND is set, but watchdog_unregister_device() does not remove it. This leaves an embedded notifier block on the PM notifier chain after the watchdog device has been unregistered. A later suspend/resume notification can then call watchdog_pm_notifier() with a stale watchdog_device pointer, or at minimum after wdd->wd_data has been cleared by watchdog_dev_unregister(). Unregister the PM notifier before tearing down the watchdog device.

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/watchdog/watchdog_core.c

What this is
WATCHDOG DEVICE DRIVERSMAINTAINERS section matched on drivers/watchdog/ · linux-watchdog@vger.kernel.org · Maintained
Kernel module
watchdog

Check it on the machine

grep -wE 'CONFIG_WATCHDOG|CONFIG_WATCHDOG_CORE' /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 watchdog

Prints 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 code. Every release below compiles the affected file into the kernels it ships.

  • bookworm, trixie, forky, sidb
b
built in on some flavours, a module on others
Build switches
CONFIG_WATCHDOG, CONFIG_WATCHDOG_CORE
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-08-15 (2 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.21%, higher than 11.0% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/watchdog

Upstream fixes

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

IntroducedFixed inCommit
5.155.15.212cd2d1b1f9930
5.156.1.1785d9b58ec6f5d
5.156.6.14589184909634e
5.156.12.97e690afea5c87
5.156.18.40298821692d44
5.157.1.5c70b5bb6f04f
5.157.2a298c7302ee9

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-74329, 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.