CVE-2026-72484

staging: most: video: avoid double free on video register failure

N/A
Published: August 15, 2026 at 05:57 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: staging: most: video: avoid double free on video register failure 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.9 ≤ v < 5.10.2614.9 ≤ v < 5.15.2124.9 ≤ v < 6.1.1784.9 ≤ v < 6.12.974.9 ≤ v < 6.18.404.9 ≤ v < 6.6.1454.9 ≤ v < 7.1.54.9 ≤ v < 7.24.9eab231c0398a91fbd294672bfe9e0ff45b368246
Vendor states this is fixed in 009d58b73500d0b49f6ae3833f8afcb0ebd9ddbb (fixed)
Vendor states this is fixed in 43078449ad6236d839e4d707954d2e36b10a6706 (fixed)
Vendor states this is fixed in 430ad4ea06a0767fb44a08e2212ceb3a996607ee (fixed)
Vendor states this is fixed in 46ea51f5b2ee1a3b40c05b7c750cbc5cabe94062 (fixed)
Vendor states this is fixed in 4928096212b78262dbbeab3b3abf2352278ce22d (fixed)
Vendor states this is fixed in 7cb1c5b32a2bfde961fff8d5204526b609bcb30a (fixed)
Vendor states this is fixed in 7fc162453cfb7b8e93edb16287a84ba0130cac38 (fixed)
Vendor states this is fixed in 80ed79787da3311f76b4d71d0ce7ab992a9e134d (fixed)
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card