GHSA-7VG7-FQGF-94J5

Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: drop the dma-buf reference when a KFD import fails

import_obj_create() takes a reference on the dma-buf for the new kgd_mem, but the error path after validating the BO doesn't drop it. Since the validation reserves the BO interruptibly, an import failing with -ERESTARTSYS leaks the exported BO with its memory, and keeps the module in use.

Importing a 64 MiB VRAM BO in a loop while getting SIGUSR1 every 20 us and another thread changes the BO's mappings:

INFO: 171821 imports, VRAM used before 65 MiB, after 129 MiB modprobe: FATAL: Module amdgpu is in use.

Drop the reference, and free the sync object and the mutex of the kgd_mem as well. With that VRAM usage returns to 65 MiB after the same test.

(cherry picked from commit b4d1eca2729840148ff2ea957724ce764ca5a94e)

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99622"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T06:17:54Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: drop the dma-buf reference when a KFD import fails\n\nimport_obj_create() takes a reference on the dma-buf for the new kgd_mem,\nbut the error path after validating the BO doesn\u0027t drop it. Since the\nvalidation reserves the BO interruptibly, an import failing with\n-ERESTARTSYS leaks the exported BO with its memory, and keeps the module\nin use.\n\nImporting a 64 MiB VRAM BO in a loop while getting SIGUSR1\nevery 20 us and another thread changes the BO\u0027s mappings:\n\n  INFO: 171821 imports, VRAM used before 65 MiB, after 129 MiB\n  modprobe: FATAL: Module amdgpu is in use.\n\nDrop the reference, and free the sync object and the mutex of the kgd_mem\nas well. With that VRAM usage returns to 65 MiB after the same test.\n\n(cherry picked from commit b4d1eca2729840148ff2ea957724ce764ca5a94e)",
  "id": "GHSA-7vg7-fqgf-94j5",
  "modified": "2026-11-20T06:32:04Z",
  "published": "2026-11-20T06:32:04Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99622"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1e65f78269a95052c2de91b4a14ee83f3e780828"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/6f300412649edf42e0eb232334a84764cd945118"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a2654cbb6a2244d8200e0505612f03bf36af2908"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fb900f8bfd8a16126affd186d21001e4c6533324"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.