CVE-2026-72484

What the bug is

comp_register_videodev() allocates a video_device with video_device_alloc() and releases it if video_register_device() fails. This can double free the video_device when __video_register_device() reaches device_register() and that call fails: video_register_device() -> __video_register_device() -> device_register() fails -> put_device(&vdev->dev) -> v4l2_device_release() -> vdev->release(vdev) -> video_device_release(vdev) comp_register_videodev() -> video_device_release(mdev->vdev) Use video_device_release_empty() while registering the device so that registration failure paths do not free mdev->vdev through vdev->release(). comp_register_videodev() then releases mdev->vdev exactly once on failure. Restore video_device_release() after successful registration so the registered device keeps its normal lifetime handling. This issue was found by a static analysis tool I am developing.

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/most/video/video.c

What this is

MOST(R) TECHNOLOGY DRIVERMAINTAINERS section matched on drivers/staging/most/ · Maintained

Kernel module

none to look for. The file would have gone into most_video, and Debian does not compile it into that module, so finding most_video in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_MOST|CONFIG_MOST_VIDEO|CONFIG_STAGING' /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 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

• bookworm, trixie, forky, sidn

n

not enabled on any flavour - this release does not build the code

Build switches

CONFIG_MOST, CONFIG_MOST_VIDEO, CONFIG_STAGING

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.22%, higher than 11.6% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

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
4.9	5.10.261	009d58b73500
4.9	5.15.212	430ad4ea06a0
4.9	6.1.178	46ea51f5b2ee
4.9	6.6.145	4928096212b7
4.9	6.12.97	80ed79787da3
4.9	6.18.40	43078449ad62
4.9	7.1.5	7fc162453cfb
4.9	7.2	7cb1c5b32a2b