CVE-2026-68383

Kernel memory disclosure via stale timeline pointer

Published Aug 10, 2026 · Updated Aug 10, 2026

Use-after-free in the Linux Xe GuC scheduler allows local users to disclose kernel memory through the DRM render node. Queue destruction frees q->name while scheduler fences retain it, so sync_file inspection copies data through a dangling timeline-name pointer. Exploitation requires low-privileged Intel Xe render-node access and yields repeatable kernel-heap disclosure or a machine crash; systems without Intel Xe are unaffected.

CVSS severity7.8
High
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in the Linux Xe GuC scheduler allows local users to disclose kernel memory through the DRM render node. Queue destruction frees q->name while scheduler fences retain it, so sync_file inspection copies data through a dangling timeline-name pointer. Exploitation requires low-privileged Intel Xe render-node access and yields repeatable kernel-heap disclosure or a machine crash; systems without Intel Xe are unaffected.

The record

CVE
CVE-2026-68383
Published
Aug 10, 2026
Updated
Aug 10, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-825
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 10, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 10, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.12.43 <6.13
  2. Affected versionversion=6.15.11 <6.16
  3. Affected versionversion=6.16.2 <6.17
  4. Affected versionversion=6.17
  5. Affected versionversion=683b0e397dad9f26a42dcacf6f7f545a77ce6c06
  6. Affected versionversion=6bd90e700b4285e6a7541e00f969cab0d696adde <299bc6d50b1bed7d1f408391736712f01a0855e2
  7. Affected versionversion=6bd90e700b4285e6a7541e00f969cab0d696adde <77fd62412431e8c80ef2ad61466bc76fe425f80a
  8. Affected versionversion=b17fcce70733c211cb5dabf54f4f9491920b1d92
  9. Affected versionversion=ba37807d08bae67de6139346a85650cab5f6145a

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=6.12.43 <6.13; version=6.15.11 <6.16; version=6.16.2 <6.17; version=6.17; version=683b0e397dad9f26a42dcacf6f7f545a77ce6c06; version=6bd90e700b4285e6a7541e00f969cab0d696adde <299bc6d50b1bed7d1f408391736712f01a0855e2; version=6bd90e700b4285e6a7541e00f969cab0d696adde <77fd62412431e8c80ef2ad61466bc76fe425f80a; version=b17fcce70733c211cb5dabf54f4f9491920b1d92; version=ba37807d08bae67de6139346a85650cab5f6145a

Published CVSS scores

7.8Linux CNACVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
5.5Red HatCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-825Expired Pointer Dereference

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo