GHSA-7RV6-JM8Q-X9P7

Vulnerability from github – Published: 2026-06-03 18:33 – Updated: 2026-06-09 21:32
VLAI
Details

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

Severity
5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-71314"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-06-03T18:16:19Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/panthor: Recover from panthor_gpu_flush_caches() failures\n\nWe have seen a few cases where the whole memory subsystem is blocked\nand flush operations never complete. When that happens, we want to:\n\n- schedule a reset, so we can recover from this situation\n- in the reset path, we need to reset the pending_reqs so we can send\n  new commands after the reset\n- if more panthor_gpu_flush_caches() operations are queued after\n  the timeout, we skip them and return -EIO directly to avoid needless\n  waits (the memory block won\u0027t miraculously work again)\n\nNote that we drop the WARN_ON()s because these hangs can be triggered\nwith buggy GPU jobs created by the UMD, and there\u0027s no way we can\nprevent it. We do keep the error messages though.\n\nv2:\n- New patch\n\nv3:\n- Collect R-b\n- Explicitly mention the fact we dropped the WARN_ON()s in the commit\n  message\n\nv4:\n- No changes",
  "id": "GHSA-7rv6-jm8q-x9p7",
  "modified": "2026-06-09T21:32:20Z",
  "published": "2026-06-03T18:33:11Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-71314"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2c899c6026fc9d39286735b30c4d8550d4ea075b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3c0a60195b37af83bbbaf223cd3a78945bace49e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/57753f2c64c033a21a7400b3a2192db1cd6c890e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8ec4f1b14a6147db07d6e51aa1d6bcc799649847"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.