In the Linux kernel, the following vulnerability has been resolved: drm/msm: make sure last_fence is always updated Update last_fence in the vm-bind path instead of ke…

Code

The project this record applies to. Exploit listings stay in References.

• Repository · git.kernel.org
• Repository · git.kernel.org

Timeline

Detection, updates, and resolution for this record.

1. Dec 16, 2025 · NIST NVD

   Detected

   In the Linux kernel, the following vulnerability has been resolved: drm/msm: make sure last_fence is always updated Update last_fence in the vm-bind path instead of kernel managed path. last_fence is used to wait for work to finish in vm_bind contexts but not used for kernel managed contexts. This fixes a bug where last_fence is not waited on context close leading to faults as resources are freed

2. Oct 14, 2026 · NIST NVD

   Updated

   In the Linux kernel, the following vulnerability has been resolved: drm/msm: make sure last_fence is always updated Update last_fence in the vm-bind path instead of kernel managed path. last_fence is used to wait for work to finish in vm_bind contexts but not used for kernel managed contexts. This fixes a bug where last_fence is not waited on context close leading to faults as resources are freed

Sources

• CVE.orgVulnerability recordCVE-2025-68314

  Official CVE identifier

  cve.org
• FIRST EPSSExploitation probabilityCVE-2025-68314

  30-day exploitation probability 0.1%

  first.org
• NIST NVDVulnerability recordCVE-2025-68314

  In the Linux kernel, the following vulnerability has been resolved: drm/msm: make sure last_fence is always updated Update last_fence in the vm-bind path instead of kernel managed path. last_fence is used to wait for work to finish in vm_bind contexts but not used for kernel m

  nvd.nist.gov

References

• Reference · git.kernel.org
• Reference · git.kernel.org