LiveActive security incident?Get immediate response
CVE Record

CVE-2025-71302: drm/panthor: fix for dma-fence safe access rules

In the Linux kernel, the following vulnerability has been resolved: drm/panthor: fix for dma-fence safe access rules Commit 506aa8b02a8d6 ("dma-fence: Add safe access helpers and document the rules") details the dma-fence safe access rules. The most common culprit is that drm_sched_fence_get_timeline_name may race with group_free_queue.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in the Linux Panthor graphics driver can violate kernel synchronization rules. The supplied CVSS rates potential confidentiality, integrity, and availability impact as high, but the sources do not describe demonstrated outcomes. Exploitation requires local, low-privileged access and no user interaction.

Executive priority

Treat as high priority where Panthor is active and local users or untrusted workloads are present. Schedule prompt kernel remediation after compatibility testing. Systems without the affected driver are lower priority, but version and backport status should be documented rather than assumed.

Technical view

The flaw involves unsafe dma-fence access in drm/panthor. drm_sched_fence_get_timeline_name may race with group_free_queue, creating unsafe concurrent access to fence-related state. The cited Linux stable commits resolve the issue, but the bundle does not identify a CWE or explain the resulting memory-safety condition.

Likely exposure

Exposure is most likely on Linux systems using the Panthor DRM driver where untrusted users or workloads have local access. The supplied affected-version data names 6.10, 6.18.16, 6.19.6, and 7.0, but its range semantics are unclear; distribution-specific kernel status requires vendor confirmation.

Exploitation context

The CVSS vector indicates a local, low-complexity attack requiring low privileges and no user interaction. The CVE is not listed as KEV, and the supplied sources provide no evidence of public exploitation or a working proof of concept.

Researcher notes

The disclosed race is between timeline-name retrieval and queue-group teardown. Three stable fix commits are cited, likely reflecting separate maintained branches. The bundle does not establish exact vulnerable ranges, root-cause CWE, reliable trigger conditions, proof-of-concept availability, or exploitation in the wild.

Mitigation direction

  • Apply a vendor-supported kernel containing the applicable cited stable fix.
  • Check distribution or appliance advisories for backport status and affected-version mapping.
  • Prioritize multi-user systems and hosts running untrusted local workloads.
  • Use vendor guidance for temporary mitigations if immediate kernel replacement is impractical.

Validation and detection

  • Inventory kernel releases across systems that may use the Panthor DRM driver.
  • Determine whether Panthor is built, loaded, or actively used on each host.
  • Confirm the installed kernel includes the applicable stable fix or vendor backport.
  • Review kernel logs for relevant graphics-driver faults, without treating their absence as proof of safety.
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-71302 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-71302Attack 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.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

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