Skip to main content

Linux Kernel CVE-2025-68747

HIGH
2025-12-24 416baaa9-dc9f-4396-8d5f-8c081fb06d67
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Local render-device access gives PR:L/AV:L; the required MMU-down race window raises complexity to AC:H; kernel UAF corruption yields full C/I/A impact.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Analysis Generated
Jul 30, 2026 - 06:59 vuln.today
CVE Published
Dec 24, 2025 - 13:16 cve.org
HIGH 7.8

DescriptionCVE.org

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.

AnalysisAI

Local privilege escalation and memory corruption in the Linux kernel's Panthor DRM driver (ARM Mali GPU) arises from a use-after-free on kernel buffer-object virtual-address nodes; when the GPU MMU is down, panthor_vm_unmap_range() returns early and leaves a va_node stuck in the drm_mm tree, so removing adjacent nodes later dereferences freed memory. A local user with GPU/render access can trigger the condition to corrupt kernel memory (CVSS 7.8, high confidentiality/integrity/availability impact). No public exploit identified at time of analysis; an upstream fix has been merged to stable trees.

Technical ContextAI

Panthor is the upstream DRM/KMS kernel driver for newer ARM Mali GPUs built on the Command Stream Frontend (CSF) architecture (e.g. Mali-G310/G510/G610/G710). It manages a per-context GPU virtual address space using the kernel's generic drm_mm range allocator to track VA nodes for buffer objects (BOs). The root cause is a use-after-free (CWE-416): panthor_vm_unmap_range() can fail when the GPU MMU is offline, and the original code bailed out of cleanup on that error, leaving the BO's va_node still linked in the drm_mm interval tree even though the surrounding object was torn down. When neighboring nodes are subsequently removed, drm_mm traverses/coalesces against the stale node, dereferencing freed memory. The fix proceeds with the remainder of the cleanup regardless of the unmap error, on the reasoning that a blocked MMU implies the whole GPU is blocked and physical memory returned to the system will not be accessed.

Affected ProductsAI

The affected component is the Linux kernel's Panthor DRM driver (drivers/gpu/drm/panthor), present in kernels shipping Panthor (introduced around 6.10 and maintained in later stable series). Exact vulnerable version ranges were not enumerated in NVD CPE data provided; the fix is distributed across multiple stable branches as shown by the four kernel.org stable commits (0612704b6f6d, 1123eadb8435, 5a0060ddfc1f, 98dd5143447a). Practically, systems using ARM Mali CSF GPUs with the mainline/stable Panthor driver are affected; downstream vendor and distribution kernels that backported Panthor should verify against these commit hashes.

RemediationAI

Upstream fix available (commit/stable backport); update to a distribution or stable kernel release that incorporates the Panthor fix referenced by the kernel.org stable commits (0612704b6f6ddf2ae223019c52148c5ac76cf70e, 1123eadb843588b361c96f53a771202b7953154f, 5a0060ddfc1fcfdb0f7b4fa1b7b3b0c436151391, 98dd5143447af0ee33551776d8b2560c35d0bc4a). Apply the patched kernel via your distribution's update channel and reboot. If immediate patching is not possible, the practical compensating control is to restrict local access to the GPU render device: limit membership of the 'render'/'video' groups and tighten permissions on /dev/dri/renderD* and /dev/dri/card* so only trusted users/processes can open the Panthor device (trade-off: this breaks GPU acceleration and containerized GPU workloads for restricted users). There is no meaningful network-level mitigation since the vector is local.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
Container suse/sl-micro/6.0/baremetal-os-container:latest Container suse/sl-micro/6.0/base-os-container:latest Container suse/sl-micro/6.0/kvm-os-container:latest Container suse/sl-micro/6.0/rt-os-container:latest Image SL-Micro Affected
Container suse/sl-micro/6.0/toolbox:latest Affected
Image SLES-Azure-3P Image SLES-Azure-Basic Image SLES-Azure-Standard Image SLES-BYOS-Azure Image SLES-BYOS-EC2 Image SLES-BYOS-GCE Image SLES-CHOST-BYOS-Aliyun Image SLES-CHOST-BYOS-Azure Image SLES-CHOST-BYOS-EC2 Image SLES-CHOST-BYOS-GCE Image SLES-CHOST-BYOS-GDC Image SLES-CHOST-BYOS-SAP-CCloud Image SLES-EC2 Image SLES-EC2-ECS Image SLES-GCE Image SLES-GCE-3P Image SLES-Hardened-BYOS-Azure Image SLES-Hardened-BYOS-EC2 Image SLES-Hardened-BYOS-GCE Image SLES-SAPCAL-Azure Image SLES-SAPCAL-EC2 Image SLES-SAPCAL-GCE Affected
Image SLES-SAP-Azure Image SLES-SAP-Azure-3P Image SLES-SAP-BYOS-Azure Image SLES-SAP-BYOS-EC2 Image SLES-SAP-BYOS-GCE Image SLES-SAP-EC2 Image SLES-SAP-GCE Image SLES-SAP-GCE-3P Affected
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-HPC-Azure Affected

Share

CVE-2025-68747 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy