LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48893: drm/i915/gt: Cleanup partial engine discovery failures

In the Linux kernel, the following vulnerability has been resolved: drm/i915/gt: Cleanup partial engine discovery failures If we abort driver initialisation in the middle of gt/engine discovery, some engines will be fully setup and some not. Those incompletely setup engines only have 'engine->release == NULL' and so will leak any of the common objects allocated. v2: - Drop the destroy_pinned_context() helper for now. It's not really worth it with just a single callsite at the moment. (Janusz)

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 cleanup bug in the Intel i915 graphics driver. If driver initialization stops partway through engine discovery, allocated engine objects may leak. The sources do not provide CVSS, CWE, impact severity, or evidence of active exploitation.

Executive priority

Treat this as routine kernel maintenance unless local context raises exposure. There is no sourced active exploitation or severity score, but kernel resource-management bugs should still be remediated through normal patch cycles.

Technical view

CVE-2022-48893 affects Linux drm/i915/gt initialization error handling. During partial GT engine discovery failure, some engines may be initialized while others lack release handlers, causing common allocations to leak. Kernel stable commits address cleanup behavior across supported branches.

Likely exposure

Exposure is likely limited to Linux systems running affected kernels with the Intel i915 DRM graphics driver path. Distribution backports may change exact exposure, so version checks should use vendor kernel advisories, not upstream version strings alone.

Exploitation context

The bundle shows no CISA KEV listing and no cited evidence of exploitation. The described flaw is an initialization failure cleanup issue, not a documented remote attack path. Practical exploitability and security impact are not established in the provided sources.

Researcher notes

The core issue is incomplete cleanup when i915 GT engine discovery aborts mid-initialization. The public record lacks CVSS, CWE, exploitability analysis, and concrete impact beyond leaked common objects, so conclusions should remain conservative.

Mitigation direction

  • Apply kernel updates from the operating system or distribution vendor.
  • Confirm updates include the referenced Linux stable fixes or distro backports.
  • Prioritize systems using Intel i915 graphics driver support.
  • Reboot after kernel updates so the fixed kernel is running.
  • If updates are unavailable, monitor vendor guidance for supported mitigations.

Validation and detection

  • Inventory Linux kernel versions across affected systems.
  • Check whether Intel i915 DRM driver support is present or loaded.
  • Confirm the running kernel includes a vendor fix for CVE-2022-48893.
  • Review distribution advisories, including Debian LTS where applicable.
  • Track remediation by running kernel, not only installed package version.
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-48893 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
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7d70a1233d11ce9286e1a04c4f1bcd263e3e405e, 7d70a1233d11ce9286e1a04c4f1bcd263e3e405e, 7d70a1233d11ce9286e1a04c4f1bcd263e3e405e, 7d70a1233d11ce9286e1a04c4f1bcd263e3e405eunaffected
LinuxLinux5.6, 0, 5.10.237, 5.15.181, 6.1.7, 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.