CVE-2026-53054
Received Received - Intake
VM_BIND UNMAP Locking Issue in Linux Kernel

Publication date: 2026-06-24

Last updated on: 2026-06-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: drm/msm: Fix VM_BIND UNMAP locking Wrong argument meant that the objs involved in UNMAP ops were not always getting locked. Since _NO_SHARE objs share a common resv with the VM (which is always locked) this would only show up with non-_NO_SHARE BOs. Patchwork: https://patchwork.freedesktop.org/patch/713898/
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-24
Last Modified
2026-06-24
Generated
2026-06-25
AI Q&A
2026-06-24
EPSS Evaluated
N/A
NVD
CVE-2026-53054
EUVD
EUVD-2026-38922
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
linux linux_kernel *
linux_kernel linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Impact Analysis

This vulnerability in the Linux kernel's drm/msm component involves improper locking during VM_BIND UNMAP operations. Specifically, objects involved in UNMAP operations were not always properly locked due to a wrong argument, which could lead to potential issues in memory management or stability when dealing with non-_NO_SHARE buffer objects.

Executive Summary

This vulnerability is in the Linux kernel's drm/msm component related to VM_BIND UNMAP locking.

The issue was caused by a wrong argument that meant the objects involved in UNMAP operations were not always properly locked.

Since _NO_SHARE objects share a common reservation with the VM (which is always locked), the problem only appeared with non-_NO_SHARE buffer objects.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53054. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart