Vulnerability-Lookup

GHSA-Q5MM-H94W-H3JF

Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 15:31

Details

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

accel: ethosu: Ensure SRAM region size matches job

It is possible for userspace to set the job SRAM size to 0, but then still have SRAM accesses in the command stream. When the job SRAM size is 0, setting the region base register is skipped and a stale base address from a prior job is used.

Check the region size against the job's SRAM size instead of just the size of the SRAM. The job's SRAM size was already checked against the total SRAM size.

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-97911"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-25T11:17:18Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel: ethosu: Ensure SRAM region size matches job\n\nIt is possible for userspace to set the job SRAM size to 0, but then still\nhave SRAM accesses in the command stream. When the job SRAM size is 0,\nsetting the region base register is skipped and a stale base address from\na prior job is used.\n\nCheck the region size against the job\u0027s SRAM size instead of just the size\nof the SRAM. The job\u0027s SRAM size was already checked against the total SRAM\nsize.",
  "id": "GHSA-q5mm-h94w-h3jf",
  "modified": "2026-09-25T15:31:44Z",
  "published": "2026-09-25T12:31:27Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97911"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2b39d680c9e0fb4d625f2916980977622e84248c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/50c27d412fedc95b8d54d477af47451a382e8cdd"
    }
  ],
  "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-97911 (GCVE-0-2026-97911)

Vulnerability from cvelistv5 – Published: 2026-09-25 10:22 – Updated: 2026-09-25 14:41

Title

accel: ethosu: Ensure SRAM region size matches job

Summary

In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Ensure SRAM region size matches job It is possible for userspace to set the job SRAM size to 0, but then still have SRAM accesses in the command stream. When the job SRAM size is 0, setting the region base register is skipped and a stale base address from a prior job is used. Check the region size against the job's SRAM size instead of just the size of the SRAM. The job's SRAM size was already checked against the total SRAM size.

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 mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/50c27d412fedc95b8…
https://git.kernel.org/stable/c/2b39d680c9e0fb4d6…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 9cff90774872ed6613b7571ce018b5b455d86890 , < 50c27d412fedc95b8d54d477af47451a382e8cdd (git) Affected: 9cff90774872ed6613b7571ce018b5b455d86890 , < 2b39d680c9e0fb4d625f2916980977622e84248c (git)
Linux	Linux	Affected: 7.2 Unaffected: 0 , < 7.2 (semver) Unaffected: 7.2.7 , ≤ 7.2.* (semver) Unaffected: 7.3-rc3 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/accel/ethosu/ethosu_job.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "50c27d412fedc95b8d54d477af47451a382e8cdd",
              "status": "affected",
              "version": "9cff90774872ed6613b7571ce018b5b455d86890",
              "versionType": "git"
            },
            {
              "lessThan": "2b39d680c9e0fb4d625f2916980977622e84248c",
              "status": "affected",
              "version": "9cff90774872ed6613b7571ce018b5b455d86890",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/accel/ethosu/ethosu_job.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.2"
            },
            {
              "lessThan": "7.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2.7",
                  "versionStartIncluding": "7.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.3-rc3",
                  "versionStartIncluding": "7.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\naccel: ethosu: Ensure SRAM region size matches job\n\nIt is possible for userspace to set the job SRAM size to 0, but then still\nhave SRAM accesses in the command stream. When the job SRAM size is 0,\nsetting the region base register is skipped and a stale base address from\na prior job is used.\n\nCheck the region size against the job\u0027s SRAM size instead of just the size\nof the SRAM. The job\u0027s SRAM size was already checked against the total SRAM\nsize."
        }
      ],
      "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 - The malformed input is a DRM_IOCTL_ETHOSU_SUBMIT job (sram_size=0, no region-2 BO handle) plus a command stream that uses region 2. A local process sends it through the /dev/accel/accelN ioctl into ethosu_ioctl_submit_job(). No remote protocol carries this data.\nAC:L - The attacker sets the stale BASEP(2) value themselves: a prior job of their own binds a BO to region 2 while sram_size is 0, then they free that BO. Their next job skips the base write in ethosu_job_hw_submit(). Both steps are ordinary submissions they control, and there is no race.\nPR:L - All ethosu ioctls, including SUBMIT, are registered with flags 0, so any unprivileged user allowed to open the accel device node (for example, the render group) can reach the flawed region-size check. Root is not required.\nUI:N - The attacker\u0027s own ioctl calls on their own BOs and command streams trigger the bug. No other user has to do anything.\nS:U - The NPU is driven by the same kernel, and no IOMMU or VM boundary is crossed (the driver sets only a 40-bit DMA mask). The impact stays within the kernel\u0027s own security authority.\nC:H - The NPU reads through a stale BASEP(2): a freed BO\u0027s physical address, or SRAM holding another client\u0027s data. The command stream can copy up to sram_size bytes from there into an attacker BO, disclosing kernel pages or other users\u0027 data.\nI:H - NPU output operations can write through the stale region-2 base into pages that were freed and reused by the kernel, or into another client\u0027s buffer. This is a DMA use-after-free write that the attacker sizes, and it can corrupt kernel memory.\nA:H - Uncontrolled DMA writes into reused kernel pages, or into a stale or reset base address, can corrupt kernel data structures, crash the system, or hang the NPU. The attacker can repeat this at will."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-25T14:41:37.359Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/50c27d412fedc95b8d54d477af47451a382e8cdd"
        },
        {
          "url": "https://git.kernel.org/stable/c/2b39d680c9e0fb4d625f2916980977622e84248c"
        }
      ],
      "title": "accel: ethosu: Ensure SRAM region size matches job",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-97911",
    "datePublished": "2026-09-25T10:22:34.639Z",
    "dateReserved": "2026-09-25T10:18:58.201Z",
    "dateUpdated": "2026-09-25T14:41:37.359Z",
    "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.

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

GHSA-Q5MM-H94W-H3JF

CVE-2026-97911 (GCVE-0-2026-97911)

Tags

Sightings

Nomenclature

Related by attack behaviour