LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68735: drm/panthor: Prevent potential UAF in group creation

In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Prevent potential UAF in group creation This commit prevents the possibility of a use after free issue in the GROUP_CREATE ioctl function, which arose as pointer to the group is accessed in that ioctl function after storing it in the Xarray. A malicious userspace can second guess the handle of a group and try to call GROUP_DESTROY ioctl from another thread around the same time as GROUP_CREATE ioctl. To prevent the use after free exploit, this commit uses a mark on an entry of group pool Xarray which is added just before returning from the GROUP_CREATE ioctl function. The mark is checked for all ioctls that specify the group handle and so userspace won't be abe to delete a group that isn't marked yet. v2: Add R-bs and fixes tags

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A locally authenticated user could race Linux Panthor GPU group creation and deletion, potentially causing use-after-free memory corruption. Successful exploitation could compromise confidentiality, integrity, or availability on affected systems. The issue is not remotely exploitable under the supplied CVSS vector.

Executive priority

Treat as high priority where untrusted users or workloads can access Panthor-enabled Linux systems. Schedule prompt kernel remediation, prioritizing shared infrastructure. Systems without the Panthor driver or relevant local access are less likely exposed, but applicability should be documented rather than assumed.

Technical view

The GROUP_CREATE ioctl exposed a group pointer after inserting it into an Xarray but before initialization safely completed. Another thread could guess the handle and invoke GROUP_DESTROY, creating a use-after-free race. The fix marks completed entries and rejects group-handle operations until that mark exists.

Likely exposure

Exposure requires an affected Linux kernel, the Panthor DRM driver, access to its userspace interface, and local low-privileged code execution. The bundle lists affected Linux versions but provides no CPEs or complete distribution-specific package mapping, so confirm applicability with kernel or distribution advisories.

Exploitation context

The supplied CVSS is 7.8: local access, low complexity, low privileges, no user interaction, and potentially high confidentiality, integrity, and availability impact. The bundle does not report CISA KEV listing or evidence of active exploitation. It describes a plausible malicious multithreaded race.

Researcher notes

The core condition is a GROUP_CREATE versus GROUP_DESTROY race involving premature Xarray visibility. The remediation adds an Xarray mark immediately before successful creation returns and checks that mark in ioctls accepting group handles. The supplied data does not establish exploit reliability, affected hardware models, or complete vulnerable version boundaries.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced Panthor fixes.
  • Check Linux distribution advisories for the corrected package version applicable to each system.
  • Where updates are delayed, restrict untrusted local access to the affected GPU interface.
  • Prioritize shared, multi-user, container-hosting, and untrusted-workload systems using Panthor.

Validation and detection

  • Inventory kernel versions and determine whether the Panthor DRM driver is present and used.
  • Compare installed kernel packages against vendor advisories and the three referenced stable commits.
  • Verify untrusted users or workloads cannot access the relevant GPU device interface.
  • After updating, confirm systems boot the corrected kernel rather than an older installed kernel.
Prepared
Confidence
medium
Sources
5

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-68735 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-68735Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxde85488138247d034eb3241840424a54d660926b, de85488138247d034eb3241840424a54d660926b, de85488138247d034eb3241840424a54d660926bunaffected
LinuxLinux6.10, 0, 6.17.13, 6.18.2, 6.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.