CVE-2025-68314: drm/msm: make sure last_fence is always updated
In the Linux kernel, the following vulnerability has been resolved:
drm/msm: make sure lastfence is always updated
Update lastfence in the vm-bind path instead of kernel managed path.
lastfence is used to wait for work to finish in vmbind contexts but not used for kernel managed contexts.
This fixes a bug where lastfence is not waited on context close leading to faults as resources are freed while in use.
Patchwork: https://patchwork.freedesktop.org/patch/680080/
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68314?
CVE-2025-68314 has been classified with a moderate severity level due to potential issues in the Linux kernel related to last_fence management.
How do I fix CVE-2025-68314?
To fix CVE-2025-68314, you should update to the latest version of the Linux kernel that includes the patch for this vulnerability.
Which Linux kernel versions are affected by CVE-2025-68314?
CVE-2025-68314 affects certain versions of the Linux kernel that do not implement the update for last_fence management.
What components are impacted by CVE-2025-68314?
CVE-2025-68314 impacts the Direct Rendering Manager (DRM) subsystem in the Linux kernel.
What is the primary cause of CVE-2025-68314?
CVE-2025-68314 is primarily caused by improper handling of the last_fence variable in vm_bind contexts within the Linux kernel.