Vulnerability-Lookup

GHSA-QQCM-W5C8-F3QV

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33

Details

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

accel/amdxdna: Use caller client for debug BO sync

amdxdna_drm_sync_bo_ioctl() looks up args->handle in the ioctl caller's drm_file. For SYNC_DIRECT_FROM_DEVICE, it then calls amdxdna_hwctx_sync_debug_bo(), but passes abo->client.

amdxdna_hwctx_sync_debug_bo() uses the passed client both as the handle namespace for debug_bo_hdl and as the owner of the hardware context xarray. Those must match the file that supplied args->handle. The BO's stored client pointer is object state, not the ioctl context.

Pass filp->driver_priv instead, matching the original handle lookup.

Severity

7.8 (High)


                  
                    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-72090"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:21:23Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/amdxdna: Use caller client for debug BO sync\n\namdxdna_drm_sync_bo_ioctl() looks up args-\u003ehandle in the ioctl caller\u0027s\ndrm_file. For SYNC_DIRECT_FROM_DEVICE, it then calls\namdxdna_hwctx_sync_debug_bo(), but passes abo-\u003eclient.\n\namdxdna_hwctx_sync_debug_bo() uses the passed client both as the handle\nnamespace for debug_bo_hdl and as the owner of the hardware context xarray.\nThose must match the file that supplied args-\u003ehandle. The BO\u0027s stored\nclient pointer is object state, not the ioctl context.\n\nPass filp-\u003edriver_priv instead, matching the original handle lookup.",
  "id": "GHSA-qqcm-w5c8-f3qv",
  "modified": "2026-08-17T06:33:09Z",
  "published": "2026-08-15T06:32:11Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72090"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/216e43d93dd49ec253052741aa476e51a8c54cd8"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7caf2a2351d4053075670ff3e26a6815da0a9e1e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-72090 (GCVE-0-2026-72090)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:52 – Updated: 2026-08-17 05:40

Title

accel/amdxdna: Use caller client for debug BO sync

Summary

In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: Use caller client for debug BO sync amdxdna_drm_sync_bo_ioctl() looks up args->handle in the ioctl caller's drm_file. For SYNC_DIRECT_FROM_DEVICE, it then calls amdxdna_hwctx_sync_debug_bo(), but passes abo->client. amdxdna_hwctx_sync_debug_bo() uses the passed client both as the handle namespace for debug_bo_hdl and as the owner of the hardware context xarray. Those must match the file that supplied args->handle. The BO's stored client pointer is object state, not the ioctl context. Pass filp->driver_priv instead, matching the original handle lookup.

Severity

7.8 (High)


                        
                          CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6992 records in the last 180 days details

References

2 references

URL	Tags
https://git.kernel.org/stable/c/216e43d93dd49ec25…
https://git.kernel.org/stable/c/7caf2a2351d405307…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 7ea0468380216c10b73633b976d33efa8c12d375 , < 216e43d93dd49ec253052741aa476e51a8c54cd8 (git) Affected: 7ea0468380216c10b73633b976d33efa8c12d375 , < 7caf2a2351d4053075670ff3e26a6815da0a9e1e (git)
Linux	Linux	Affected: 6.19 Unaffected: 0 , < 6.19 (semver) Unaffected: 7.1.5 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/accel/amdxdna/amdxdna_gem.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "216e43d93dd49ec253052741aa476e51a8c54cd8",
              "status": "affected",
              "version": "7ea0468380216c10b73633b976d33efa8c12d375",
              "versionType": "git"
            },
            {
              "lessThan": "7caf2a2351d4053075670ff3e26a6815da0a9e1e",
              "status": "affected",
              "version": "7ea0468380216c10b73633b976d33efa8c12d375",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/accel/amdxdna/amdxdna_gem.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.19"
            },
            {
              "lessThan": "6.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.5",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel/amdxdna: Use caller client for debug BO sync\n\namdxdna_drm_sync_bo_ioctl() looks up args-\u003ehandle in the ioctl caller\u0027s\ndrm_file. For SYNC_DIRECT_FROM_DEVICE, it then calls\namdxdna_hwctx_sync_debug_bo(), but passes abo-\u003eclient.\n\namdxdna_hwctx_sync_debug_bo() uses the passed client both as the handle\nnamespace for debug_bo_hdl and as the owner of the hardware context xarray.\nThose must match the file that supplied args-\u003ehandle. The BO\u0027s stored\nclient pointer is object state, not the ioctl context.\n\nPass filp-\u003edriver_priv instead, matching the original handle lookup."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Exploitation requires DRM_IOCTL_AMDXDNA_SYNC_BO via ioctl on the local AMD XDNA accel node (/dev/accel/accel*); amdxdna has no network, Bluetooth, or physical-bus entry to amdxdna_drm_sync_bo_ioctl() or amdxdna_hwctx_sync_debug_bo().\nAC:L - An attacker with two DRM clients can share debug buffer objects via dma-buf and issue SYNC_DIRECT_FROM_DEVICE to force abo-\u003eclient != filp-\u003edriver_priv; handle-index collisions in the victim client\u0027s namespace are attacker-influencable without uncontrollable timing or layout.\nPR:L - AMDXDNA_SYNC_BO is registered without DRM_ROOT_ONLY; any unprivileged local user permitted to open the AMD NPU accel device (typically via render/video group on Ryzen AI laptops or cloud NPU guests) can reach the bug without real root.\nUI:N - No victim interaction is required; a local attacker can open the accel device, create or import buffer objects, and trigger SYNC_DIRECT_FROM_DEVICE from their own process or a second cooperating local client in typical multi-process ML workloads.\nS:U - The flaw causes cross-DRM-client handle-namespace and hwctx confusion within the same kernel on one host; it does not cross VM, hypervisor, IOMMU, or SR-IOV security boundaries into another authority.\nC:H - Passing abo-\u003eclient re-resolves the ioctl handle in another client\u0027s drm_file and hwctx xarray, so SYNC_DEBUG_BO can DMA firmware debug data from a victim hwctx into attacker-mapped or attacker-chosen device memory, disclosing cross-context NPU/firmware contents.\nI:H - Mismatched client/handle resolution can bind SYNC_DEBUG_BO to the wrong hwctx and BO, directing firmware device-to-host DMA sync to incorrect device-heap offsets and corrupting another client\u0027s NPU buffer allocations or metadata.\nA:H - Erroneous cross-context firmware mailbox sync on an invalid or foreign hwctx can fault driver error paths, hang the mailbox channel, or destabilize the NPU stack, denying accelerator service to local workloads on the affected host."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:40:10.207Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/216e43d93dd49ec253052741aa476e51a8c54cd8"
        },
        {
          "url": "https://git.kernel.org/stable/c/7caf2a2351d4053075670ff3e26a6815da0a9e1e"
        }
      ],
      "title": "accel/amdxdna: Use caller client for debug BO sync",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-72090",
    "datePublished": "2026-08-15T05:52:37.524Z",
    "dateReserved": "2026-08-09T03:40:39.905Z",
    "dateUpdated": "2026-08-17T05:40:10.207Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

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

Order JSON

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

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.

Action not permitted