LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50745: staging: media: tegra-video: fix device_node use after free

In the Linux kernel, the following vulnerability has been resolved: staging: media: tegra-video: fix device_node use after free At probe time this code path is followed: * tegra_csi_init * tegra_csi_channels_alloc * for_each_child_of_node(node, channel) -- iterates over channels * automatically gets 'channel' * tegra_csi_channel_alloc() * saves into chan->of_node a pointer to the channel OF node * automatically gets and puts 'channel' * now the node saved in chan->of_node has refcount 0, can disappear * tegra_csi_channels_init * iterates over channels * tegra_csi_channel_init -- uses chan->of_node After that, chan->of_node keeps storing the node until the device is removed. of_node_get() the node and of_node_put() it during teardown to avoid any risk.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-safety bug in the Tegra video driver path. It can leave a pointer to device-tree data after its reference is released. The public record does not provide CVSS, impact details, or evidence of exploitation. Business urgency is mainly for organizations running NVIDIA Tegra-based Linux devices with camera/CSI functionality.

Executive priority

Moderate monitoring priority unless you operate Tegra-based camera or embedded Linux products. For those assets, treat as a kernel maintenance update and confirm vendor patches. No evidence in the supplied sources supports emergency response for broad enterprise Linux fleets.

Technical view

During Tegra CSI probe, the driver stores a child device_node pointer in chan->of_node after iteration releases the reference. Later initialization and device removal can use that stale pointer. The kernel fix takes a reference with of_node_get() and releases it during teardown with of_node_put().

Likely exposure

Exposure appears limited to Linux systems using the staging media tegra-video/Tegra CSI code path. This most likely affects embedded or ARM-based Tegra platforms, not general Linux servers. Exact distro exposure depends on vendor kernels and backports.

Exploitation context

The provided sources do not report active exploitation, public exploit code, or a CVSS score. The CVE is not listed as KEV in the supplied data. Practical exploitability and security impact are not established by the available record.

Researcher notes

Key evidence is the upstream kernel fix description. The issue is a reference-counting use-after-free in the staging media tegra-video driver. The record lacks CVSS, CWE, proof of exploitation, and detailed affected-version semantics, so impact assessment requires platform-specific validation.

Mitigation direction

  • Inventory Linux systems using Tegra video, CSI, or affected vendor kernels.
  • Update to a Linux stable or vendor kernel containing the referenced fix commits.
  • If updates are unavailable, check vendor guidance for backports or temporary mitigations.
  • Prioritize embedded devices where camera or CSI functionality is enabled.

Validation and detection

  • Confirm running kernel version and vendor patch level against referenced stable commits.
  • Review kernel source or package changelog for the tegra-video device_node fix.
  • Verify whether the Tegra CSI or video driver is built, loaded, or used.
  • Track vendor advisories because CVSS and operational impact are not provided.
Prepared
Confidence
medium
Sources
7

Public sources used

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-50745 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
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1ebaeb09830f36c1111b72a95420814225bd761c, 1ebaeb09830f36c1111b72a95420814225bd761c, 1ebaeb09830f36c1111b72a95420814225bd761c, 1ebaeb09830f36c1111b72a95420814225bd761c, 1ebaeb09830f36c1111b72a95420814225bd761cunaffected
LinuxLinux5.10, 0, 5.10.163, 5.15.87, 6.0.18, 6.1.4, 6.2affected
Weakness

CWE details

No CWE listed

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