CVE-2025-71314 Details
Description
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Recover from panthor_gpu_flush_caches() failures We have seen a few cases where the whole memory subsystem is blocked and flush operations never complete. When that happens, we want to: - schedule a reset, so we can recover from this situation - in the reset path, we need to reset the pending_reqs so we can send new commands after the reset - if more panthor_gpu_flush_caches() operations are queued after the timeout, we skip them and return -EIO directly to avoid needless waits (the memory block won't miraculously work again) Note that we drop the WARN_ON()s because these hangs can be triggered with buggy GPU jobs created by the UMD, and there's no way we can prevent it. We do keep the error messages though. v2: - New patch v3: - Collect R-b - Explicitly mention the fact we dropped the WARN_ON()s in the commit message v4: - No changes
A vulnerability has been identified in the Linux kernel's handling of cache flush operations for the Panthor GPU. This issue can cause the entire memory subsystem to become blocked, with flush operations failing to complete. The vulnerability arises from the GPU's logical block not properly managing cache flush requests, especially when these requests are queued after a timeout. The problem can be triggered by faulty GPU jobs created by the User Mode Driver (UMD), leading to unresponsive memory blocks.
The vulnerability has been addressed in the Linux kernel stable tree. Users can upgrade to the latest version to apply the fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2c899c6026fc9d39286735b30c4d8550d4ea075b | kernel.org | Patch |
| https://git.kernel.org/stable/c/3c0a60195b37af83bbbaf223cd3a78945bace49e | kernel.org | Patch |
| https://git.kernel.org/stable/c/57753f2c64c033a21a7400b3a2192db1cd6c890e | kernel.org | Patch |
| https://git.kernel.org/stable/c/8ec4f1b14a6147db07d6e51aa1d6bcc799649847 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.10, < 6.12.75 >= 6.13, < 6.18.14 >= 6.19, < 6.19.4 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 22, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 9, 2026 | Initial Analysis | [email protected] |
| Jun 3, 2026 | New CVE Received | kernel.org |