# drm/xe/guc: Keep scheduler timeline name alive

CVE record · `CVE-2026-68383`

- **Identifiers:** `CVE-2026-68383`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 10 Aug 2026, 12:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `b17fcce70733c211cb5dabf54f4f9491920b1d92 to before eac2839585741e6c1b4af261a0b58bca0d6f5436` (git)
  - affected: `6bd90e700b4285e6a7541e00f969cab0d696adde to before 88c38ff74f8345fcf8852549f94025754019b037` (git)
  - affected: `6bd90e700b4285e6a7541e00f969cab0d696adde to before 77fd62412431e8c80ef2ad61466bc76fe425f80a` (git)
  - affected: `6bd90e700b4285e6a7541e00f969cab0d696adde to before 299bc6d50b1bed7d1f408391736712f01a0855e2` (git)
  - affected: `ba37807d08bae67de6139346a85650cab5f6145a` (git)
  - affected: `683b0e397dad9f26a42dcacf6f7f545a77ce6c06` (git)
  - affected: `6.12.43 to before 6.12.114` (semver)
  - affected: `6.15.11 to before 6.16` (semver)
  - affected: `6.16.2 to before 6.17` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.17`
  - unaffected: `before 6.17` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.57 to 6.18.*, inclusive` (semver)
  - unaffected: `7.1.6 to 7.1.*, inclusive` (semver)
  - unaffected: `7.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0014, the 3rd percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 10 Aug 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-68383](https://www.cve.org/CVERecord?id=CVE-2026-68383)
- [NVD: CVE-2026-68383](https://nvd.nist.gov/vuln/detail/CVE-2026-68383)

### References from the CNA

- <https://git.kernel.org/stable/c/eac2839585741e6c1b4af261a0b58bca0d6f5436>
- <https://git.kernel.org/stable/c/88c38ff74f8345fcf8852549f94025754019b037>
- <https://git.kernel.org/stable/c/77fd62412431e8c80ef2ad61466bc76fe425f80a>
- <https://git.kernel.org/stable/c/299bc6d50b1bed7d1f408391736712f01a0855e2>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-68383>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-68383/>. Everything for agents: <https://agentprime.io/llms.txt>.
