CVE-2026-93180: drm/panthor: Fix NPD issue on partial unmap of an evicted BO

Published Sep 17, 2026

Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/panthor: Fix NPD issue on partial unmap of an evicted BO

This commit fixes the NULL pointer dereference issue that would have happened on the split of GPU mapping due to partial unmap of an evicted BO. There is a logic to handle the partial unmap of huge pages when the GPU mapping is split. That logic was not being completely skipped for the VMA of an evicted BO and that resulted in a NPD possibility for the 'bo->backing.pages' pointer, which is set to NULL when pages of a BO are released on eviction.

Following dump was seen when a partial unmap was exercised for an evicted BO. Unable to handle kernel paging request at virtual address 0000000000002000 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=00000008842e8000 [0000000000002000] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] SMP <snip> pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : iovamappedashugepage+0x20/0x68 [panthor] lr : panthorgpuvasmstepremap+0x39c/0x498 [panthor] sp : ffff800086193920 x29: ffff800086193920 x28: ffff800086193a18 x27: ffff800086193b80 x26: 0000000000400000 x25: 0000000000810000 x24: 0000000000400000 x23: ffff000808af1800 x22: 0000000000a00000 x21: ffff800086193a00 x20: ffff000806fd3f00 x19: 0000000000410000 x18: 00000000ffffffff x17: 0000000000000000 x16: 0000000000000000 x15: ffff800083ce2d83 x14: 0000000000000000 x13: 3120646574636976 x12: 6520303030303138 x11: 2d30303030313420 x10: ffff8000836e6c80 x9 : ffff80007bfc889c x8 : 3fffffffffffefff x7 : ffff8000836e6c80 x6 : 0000000000000000 x5 : ffff00097ef19088 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 0000000000010000 x1 : 0000000000000400 x0 : 0000000000000000 Call trace: iovamappedashugepage+0x20/0x68 [panthor] (P) opremapcb.isra.0+0x70/0xb0 drmgpuvmsmunmap+0xf8/0x1c0 drmgpuvmsmunmap+0x40/0x60 panthorvmexecop+0xa0/0x168 [panthor] panthorvmbindexecsyncop+0x8c/0xb8 [panthor] panthorioctlvmbind+0xbc/0x170 [panthor] drmioctlkernel+0xc0/0x140 drmioctl+0x20c/0x500 arm64sysioctl+0xb4/0x118 invokesyscall+0x5c/0x120 el0svccommon.constprop.0+0x48/0xf8 doel0svc+0x28/0x40 el0svc+0x38/0x128 el0t64synchandler+0xa0/0xe8 el0t64sync+0x198/0x1a0 Code: 8b030021 cb020021 f940b800 d34cfc21 (f8617801) ---[ end trace 0000000000000000 ]---

v2: Fix indentation

Affected Software

1 affected component

Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade drm/panthor to a version that resolves this vulnerability.
Patch drm/panthor: Fix NPD issue on partial unmap of an evicted BO

Event History

Sep 17, 2026

CVE Published

via MITRE·04:12 PM

Data Sourced

via MITRE·04:12 PM

Description

Frequently Asked Questions

Which systems are exposed to this issue?

Systems using the Linux kernel's Panthor DRM driver are exposed when a GPU buffer object has been evicted and its GPU mapping is partially unmapped, causing the mapping to be split.

What is the likely impact if the issue is triggered?

The kernel can dereference the NULL bo->backing.pages pointer and generate a kernel paging-request Oops. The provided fault example is an ARM64 data abort at virtual address 0x2000.

How can I tell whether this has already occurred?

Review kernel logs for an "Unable to handle kernel paging request" or "Internal error: Oops" associated with a partial unmap of an evicted buffer object in the Panthor DRM driver.