CVE-2022-50499

media: dvb-core: Fix double free in dvb_register_device()

HIGH
7.8
CVSS Score
Published: October 4, 2025 at 03:43 PM UTC
Updated: June 17, 2026 at 05:23 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
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: media: dvb-core: Fix double free in dvb_register_device() In function dvb_register_device() -> dvb_register_media_device() -> dvb_create_media_entity(), dvb->entity is allocated and initialized. If the initialization fails, it frees the dvb->entity, and return an error code. The caller takes the error code and handles the error by calling dvb_media_device_free(), which unregisters the entity and frees the field again if it is not NULL. As dvb->entity may not NULLed in dvb_create_media_entity() when the allocation of dvbdev->pad fails, a double free may occur. This may also cause an Use After free in media_device_unregister_entity(). Fix this by storing NULL to dvb->entity when it is freed.

Affected

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

v ≥ 5.2.19v ≥ 5.3.44.14.147 ≤ v < 4.14.3034.19.77 ≤ v < 4.19.2704.9.195 ≤ v < 4.9.3375.11 ≤ v < 5.15.875.16 ≤ v < 6.0.185.2.19 ≤ v < 5.35.3.4 ≤ v < 5.45.3.4 ≤ v < 5.4.2295.4 ≤ v < 5.10.1635.4 ≤ v < 5.15.875.4 ≤ v < 5.4.2295.4 ≤ v < 6.0.185.4 ≤ v < 6.1.45.4 ≤ v < 6.25.5 ≤ v < 5.10.1636.1 ≤ v < 6.1.41399a136127bfe1b9bb7c951d9851da62a519121202be5d6e46f682b9d1d79cd4dc6ab726e62ef1c4.14.1474.19.774.9.1954df2427a5148093987437054bb82da4d014dcd595.2.195.3.45.48c17f6f5d0d6aab72a2af25c9911ac66e984be069db28659aa893c68f162b11fd63bb7f6a713e52ffcd5ce4b3936242e6679875a4d3c3acfc8743e15
Vendor states this is fixed in 0588b12c418c3e4f927ced11f27b02ef4a5bfb07 (fixed)
Vendor states this is fixed in 123eddf92a114e03919942641d2c2b1f4ca56ea6 (fixed)
Vendor states this is fixed in 6b0d0477fce747d4137aa65856318b55fba72198 (fixed)
Vendor states this is fixed in 70bc51303871159796b55ba1a8f16637b46c2511 (fixed)
Vendor states this is fixed in 772892b29ac50c2c5e918fc80104aa6ede81d837 (fixed)
Vendor states this is fixed in 7dd5a68cdbbbe7fc67ba701cb52ba10d8ba149f8 (fixed)
Vendor states this is fixed in acf984a3718c2458eb9e08b6714490a04f213c58 (fixed)
Vendor states this is fixed in b21f62b49ee9c3e0216d685d9cfd6003e5727271 (fixed)
Vendor states this is fixed in e9a78485b658361fab6a5547377be6c1af6f1b3d (fixed)
Vendor states this is fixed in 4.14.303 (unaffected)
Vendor states this is fixed in 4.19.270 (unaffected)
Vendor states this is fixed in 4.9.337 (unaffected)
Vendor states this is fixed in 5.10.163 (unaffected)
Vendor states this is fixed in 5.15.87 (unaffected)
Affected range stops below 5.3, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 5.4.229 (unaffected)
Vendor states this is fixed in 6.0.18 (unaffected)
Vendor states this is fixed in 6.1.4 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-415

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