CVE-2022-49216: drm/tegra: Fix reference leak in tegra_dsi_ganged_probe
In the Linux kernel, the following vulnerability has been resolved:
drm/tegra: Fix reference leak in tegra_dsi_ganged_probe
The reference taken by 'of_find_device_by_node()' must be released when
not needed anymore. Add put_device() call to fix this.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49216 is a Linux kernel flaw in the NVIDIA Tegra display driver path. It leaks a device reference during DSI ganged probing. The published impact is local denial of service, not data theft or privilege escalation. Systems are mainly exposed if they run affected Linux kernels with relevant Tegra DRM/DSI functionality.
Executive priority
Handle as a routine-to-priority availability fix for Tegra Linux fleets. It is not presented as remotely exploitable or actively exploited, but it can affect device stability. Patch during normal kernel maintenance unless critical Tegra devices are exposed to untrusted local users.
Technical view
The issue is in drm/tegra tegra_dsi_ganged_probe. A reference acquired by of_find_device_by_node() was not released when no longer needed. The kernel fix adds put_device(). CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, high availability impact only.
Likely exposure
Likely limited to Linux systems using affected kernel builds and Tegra display/DSI components. General-purpose Linux servers without Tegra DRM/DSI hardware or driver use are less likely to be exposed, based on the provided description.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not marked KEV. The CVSS vector requires local access with low privileges and targets availability. The sources do not provide exploit details or evidence of weaponization.
Researcher notes
The public record is concise and does not name a CWE. Affected-version semantics in the provided bundle are not fully clear, so validation should rely on vendor kernel package status or presence of the stable fix commit rather than version strings alone.
Mitigation direction
Check your Linux distribution or device vendor advisory for a kernel update including the fix.
Prioritize updates for Tegra-based systems using DRM/DSI display functionality.
If maintaining kernels, ensure the relevant stable kernel commit is included.
Where updates are unavailable, review vendor guidance for safe operational workarounds.
Validation and detection
Inventory Linux kernel versions on Tegra-based devices.
Confirm whether Tegra DRM/DSI support is enabled or in use.
Check kernel source or package changelog for the referenced stable commit.
Use vendor security advisories to map package versions to the CVE fix.
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-49216 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.