dbcve.org
Linux KernelOperating system · Linux

CVE-2022-50499

HIGH · 7.8 CVSS v3.1 Published 2025-10-04
Fix available
A fix is available. Upgrade to 4.9.337 / 4.14.303 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-415

The same block of memory is freed twice, corrupting the allocator's bookkeeping in ways an attacker can shape toward code execution. It usually stems from tangled ownership of a pointer. The fix is clear, single ownership of each allocation and clearing pointers once they are freed.

General guidance for the double free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 4.9.195, < 4.9.337>= 4.14.147, < 4.14.303>= 4.19.77, < 4.19.270>= 5.2.19, < 5.3>= 5.3.4, < 5.4.229>= 5.5, < 5.10.163>= 5.11, < 5.15.87>= 5.16, < 6.0.18>= 6.1, < 6.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.9.337 / 4.14.303 / 4.19.270 or later
Fixed in 4.9.3374.14.3034.19.270
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux Kernel 4.9.337+ / 4.14.303+ / 4.19.270+ / 5.3+ (depending on which branch you are on)

  1. Identify the currently running Linux kernel version using `uname -r`
  2. Determine which kernel branch (4.9.x, 4.14.x, 4.19.x, or 5.2.x) your version belongs to
  3. Upgrade to a patched kernel version: 4.9.337 or later for 4.9.x kernels; 4.14.303 or later for 4.14.x kernels; 4.19.270 or later for 4.19.x kernels; 5.3 or later for 5.2.x kernels
  4. On distributions like RHEL/CentOS, use `yum update kernel` or `dnf update kernel`
  5. On Debian/Ubuntu, use `apt-get update && apt-get install linux-image-<version>`
  6. Reboot into the new kernel: `systemctl reboot`
  7. Verify the new kernel version with `uname -r`
Caveat Kernel upgrades may require rebooting and could introduce compatibility issues with out-of-tree kernel modules or proprietary drivers; test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-50499 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-50499 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data