LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68747: drm/panthor: Fix UAF on kernel BO VA nodes

In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Fix UAF on kernel BO VA nodes If the MMU is down, panthor_vm_unmap_range() might return an error. We expect the page table to be updated still, and if the MMU is blocked, the rest of the GPU should be blocked too, so no risk of accessing physical memory returned to the system (which the current code doesn't cover for anyway). Proceed with the rest of the cleanup instead of bailing out and leaving the va_node inserted in the drm_mm, which leads to UAF when other adjacent nodes are removed from the drm_mm tree.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in Linux’s panthor GPU driver can leave a freed memory-management object referenced after an error. A local, low-privileged user may be able to trigger memory corruption, potentially compromising confidentiality, integrity, and availability. Exposure requires an affected kernel and use of the panthor driver.

Executive priority

Treat as a high-priority local privilege-boundary issue on systems using panthor, especially shared or untrusted-user environments. Inventory affected endpoints promptly and deploy vendor-supported corrected kernels. Systems without the driver in use have lower practical urgency, but version and driver status should be verified rather than assumed.

Technical view

When the MMU is down, panthor_vm_unmap_range() may fail. Cleanup previously stopped while leaving a VA node in the drm_mm tree. Later removal of adjacent nodes can access that freed node, causing a use-after-free. The linked Linux stable commits change cleanup behavior so it continues after the unmap error.

Likely exposure

Most relevant to Linux systems running an affected kernel with the panthor DRM driver present and operational. The supplied version data identifies affected releases but is ambiguously flattened, so organizations should map their exact kernel build against the linked stable fixes. Remote-only attackers are not indicated by the CVSS vector.

Exploitation context

The supplied CVSS vector describes local access, low privileges, low complexity, and no user interaction, with potentially high impact. CVE-2025-68747 is not marked as CISA KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.

Researcher notes

The root condition is incomplete cleanup after an MMU unmap failure, leaving a stale drm_mm VA node that becomes unsafe during adjacent-node removal. The source bundle contains four stable fixes, but its affected-version list is not sufficiently structured to establish precise vulnerable ranges. No CWE, exploitation evidence, or confirmed attack outcome beyond CVSS impact is supplied.

Mitigation direction

  • Install a vendor-supported kernel containing the appropriate linked Linux stable fix.
  • Prioritize multi-user systems where untrusted local users can access the panthor driver.
  • Consult the Linux or distribution vendor when fixed-build status is unclear.
  • Restrict untrusted local access until the corrected kernel can be deployed.

Validation and detection

  • Record the running kernel release, package build, and distribution security status.
  • Determine whether the panthor driver is present, enabled, and used on each system.
  • Compare vendor kernel sources against the four linked stable fix commits.
  • Confirm the updated kernel is running after remediation, not merely installed.
  • Use defensive regression testing to verify GPU workloads remain stable after updating.
Prepared
Confidence
high
Sources
6

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-68747 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
5Source 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-68747Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8a1cc07578bf42d85f008316873d710ff684dd29, 8a1cc07578bf42d85f008316873d710ff684dd29, 8a1cc07578bf42d85f008316873d710ff684dd29, 8a1cc07578bf42d85f008316873d710ff684dd29unaffected
LinuxLinux6.10, 0, 6.12.63, 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.