CVE-2026-72484

UnknownEPSS 0.21%

Last modified

CVE-2026-72484 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.21%

11.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= eab231c0398a91fbd294672bfe9e0ff45b368246, < 009d58b73500d0b49f6ae3833f8afcb0ebd9ddbb; >= eab231c0398a91fbd294672bfe9e0ff45b368246, < 430ad4ea06a0767fb44a08e2212ceb3a996607ee; >= eab231c0398a91fbd294672bfe9e0ff45b368246, < 46ea51f5b2ee1a3b40c05b7c750cbc5cabe94062; >= eab231c0398a91fbd294672bfe9e0ff45b368246, < 4928096212b78262dbbeab3b3abf2352278ce22d; >= eab231c0398a91fbd294672bfe9e0ff45b368246, < 80ed79787da3311f76b4d71d0ce7ab992a9e134d; >= eab231c0398a91fbd294672bfe9e0ff45b368246, < 43078449ad6236d839e4d707954d2e36b10a6706; >= eab231c0398a91fbd294672bfe9e0ff45b368246, < 7fc162453cfb7b8e93edb16287a84ba0130cac38; >= eab231c0398a91fbd294672bfe9e0ff45b368246, < 7cb1c5b32a2bfde961fff8d5204526b609bcb30a
LinuxLinux4.9

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-72484?
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.
How severe is CVE-2026-72484?
Severity scoring for CVE-2026-72484 is pending analysis. The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72484?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-72484?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST