LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22096: drm/msm/gem: Fix error code msm_parse_deps()

In the Linux kernel, the following vulnerability has been resolved: drm/msm/gem: Fix error code msm_parse_deps() The SUBMIT_ERROR() macro turns the error code negative. This extra '-' operation turns it back to positive EINVAL again. The error code is passed to ERR_PTR() and since positive values are not an IS_ERR() it eventually will lead to an oops. Delete the '-'. Patchwork: https://patchwork.freedesktop.org/patch/637625/

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-22096 is a Linux kernel bug in the Qualcomm MSM DRM/GEM graphics path. A wrong error-code sign can make the kernel treat a failure as a valid pointer, leading to a kernel oops. Business impact is most likely service disruption on affected Linux systems, but public sources do not provide CVSS or exploitation evidence.

Executive priority

Treat as a targeted stability and availability issue, not a confirmed internet-wide emergency. Prioritize patching Linux fleets that use Qualcomm MSM graphics drivers or embedded/mobile Linux kernels, and rely on vendor advisories for exact exposure.

Technical view

In drm/msm/gem msm_parse_deps(), SUBMIT_ERROR() already returns a negative error. An extra negation made EINVAL positive before ERR_PTR(). Because positive values are not caught by IS_ERR(), execution can later dereference invalid state and oops. The kernel stable references remove the extra negation.

Likely exposure

Exposure appears limited to Linux kernels with the msm DRM/GEM code path present and reachable. The CVE data lists Linux 6.14-line impact and stable fix references, but distribution-specific affected versions require vendor mapping.

Exploitation context

No KEV listing or cited source indicates active exploitation. The described impact is a kernel oops from incorrect error handling, suggesting local denial-of-service risk where the affected DRM path is accessible. Public sources do not document remote exploitation.

Researcher notes

Evidence is limited to the CVE description and kernel stable commits. No CVSS, CWE, exploit status, or detailed attack preconditions are provided. Avoid broad claims beyond msm DRM/GEM reachability and potential kernel oops.

Mitigation direction

  • Check kernel vendor advisories for CVE-2025-22096 applicability.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize devices using Qualcomm MSM DRM/GPU functionality.
  • If updates are unavailable, assess whether the msm DRM driver is needed.

Validation and detection

  • Inventory Linux kernel versions across affected device classes.
  • Confirm whether msm DRM/GEM support is enabled or loaded.
  • Check vendor kernel changelogs for the two referenced stable commits.
  • Review crash logs for related kernel oops events.
Prepared
Confidence
medium
Sources
4

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-2025-22096 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
3Source 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
LinuxLinux866e43b945bf98f8e807dfa45eca92f931f3a032, 866e43b945bf98f8e807dfa45eca92f931f3a032unaffected
LinuxLinux6.14, 0, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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