LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50175: media: tw686x: Fix memory leak in tw686x_video_init

In the Linux kernel, the following vulnerability has been resolved: media: tw686x: Fix memory leak in tw686x_video_init video_device_alloc() allocates memory for vdev, when video_register_device() fails, it doesn't release the memory and leads to memory leak, call video_device_release() to fix this.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in the tw686x media driver. If device registration fails during initialization, allocated memory is not released. The published record provides no CVSS score, no CWE, and no evidence of active exploitation, so business urgency depends on whether affected kernels and this driver are present.

Executive priority

Treat as a targeted kernel hygiene issue, not an emergency based on current evidence. Include it in normal Linux patch cycles, with faster handling for systems using the affected media driver or where kernel resource exhaustion would materially affect operations.

Technical view

The flaw is in tw686x_video_init. video_device_alloc() allocates vdev, but on video_register_device() failure the error path did not release it. The upstream fix calls video_device_release() on that failure path. The record lists Linux kernel versions and stable commit references, but does not describe privilege requirements or exploitability.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds where the tw686x media driver code is included and reachable. The source bundle does not identify distributions, appliances, or cloud images, so organizations should map this to their own kernel packages and hardware/driver usage.

Exploitation context

The source bundle does not report public exploitation, weaponized details, or CISA KEV listing. The failure condition is an initialization error path, which suggests denial-of-service or resource exhaustion concerns may be relevant, but impact is not fully characterized in the provided sources.

Researcher notes

Key missing details are CVSS, CWE classification, exploit preconditions, and distribution-specific affected ranges. The strongest grounded facts are the memory leak cause, the failed video_register_device() path, the video_device_release() fix, and the absence of KEV evidence in the bundle.

Mitigation direction

  • Apply kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for backported fixed kernel packages.
  • Prioritize systems that include or load the tw686x media driver.
  • Track vendor guidance if no package fix is available yet.

Validation and detection

  • Inventory Linux kernel versions against the CVE record and vendor advisories.
  • Determine whether the tw686x media driver is built, packaged, or loaded.
  • Confirm deployed kernels contain one of the referenced stable fixes.
  • Review kernel logs for relevant device registration failures if exposure exists.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50175 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux704a84ccdbf19fdce9adfda0b936dfdcac52fa49, 704a84ccdbf19fdce9adfda0b936dfdcac52fa49, 704a84ccdbf19fdce9adfda0b936dfdcac52fa49, 704a84ccdbf19fdce9adfda0b936dfdcac52fa49, 704a84ccdbf19fdce9adfda0b936dfdcac52fa49unaffected
LinuxLinux4.7, 0, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.