LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49336: drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem

In the Linux kernel, the following vulnerability has been resolved: drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem When the mapping is already reaped the unmap must be a no-op, as we would otherwise try to remove the mapping twice, corrupting the involved data structures.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-49336 is a Linux kernel flaw in the etnaviv DRM GPU driver. If a GPU memory mapping was already cleaned up, the kernel could try to remove it again, corrupting internal data structures. The public record does not provide CVSS, impact scope, or confirmed exploitation.

Executive priority

Handle through the normal kernel patch process unless exposed devices are business-critical or externally managed at scale. Escalate if fleet inventory confirms etnaviv usage and vendor fixes are available.

Technical view

The issue is in etnaviv_iommu_unmap_gem. The fix makes unmapping a previously reaped mapping a no-op, preventing a double removal of mapping state and related data-structure corruption. Affected Linux kernel version data is listed, but the source bundle does not detail attacker prerequisites or impact class.

Likely exposure

Exposure is most likely on Linux systems or embedded devices using the etnaviv DRM driver for Vivante GPU hardware. Generic Linux presence alone is not enough to confirm exposure from the supplied evidence.

Exploitation context

The source bundle does not report active exploitation, and KEV status is false. No public exploit details are included. Treat this as a kernel driver memory-management flaw requiring asset-specific validation.

Researcher notes

The record names data-structure corruption from double unmapping but lacks CVSS, CWE, exploitability notes, and privilege requirements. Analysis should stay tied to kernel commit evidence and distribution-specific backport status.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Prioritize systems using the etnaviv DRM driver or Vivante GPU hardware.
  • Check Linux distribution advisories for fixed package versions.
  • Avoid direct wrangler or deployment assumptions; this is an OS/kernel remediation item.

Validation and detection

  • Inventory Linux assets for etnaviv DRM driver usage.
  • Check running kernel versions against vendor fixed releases.
  • Confirm kernel source or package changelog includes the referenced stable commits.
  • Review crash telemetry for GPU driver or IOMMU mapping anomalies.
Prepared
Confidence
medium
Sources
8

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-49336 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
7Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa8c21a5451d831e67b7a6fb910f9ca8bc7b43554, a8c21a5451d831e67b7a6fb910f9ca8bc7b43554, a8c21a5451d831e67b7a6fb910f9ca8bc7b43554, a8c21a5451d831e67b7a6fb910f9ca8bc7b43554, a8c21a5451d831e67b7a6fb910f9ca8bc7b43554, a8c21a5451d831e67b7a6fb910f9ca8bc7b43554unaffected
LinuxLinux4.5, 0, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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