Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-68383: drm/xe/guc: Keep scheduler timeline name alive

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 299bc6d50b1bed7d1f408391736712f01a0855e2, 6.12.114, 6.16.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 299bc6d50b1bed7d1f408391736712f01a0855e2, 6.12.114, 6.16 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Keep scheduler timeline name alive The scheduler keeps a pointer to the timeline name, but q->name is freed with the exec queue while scheduler fences can still reference it. Store the name in struct xe_guc_exec_queue so it shares the scheduler's RCU-deferred lifetime. (cherry picked from commit 41075f0eb5dcbd3b065d15f15ef7bbe9315188e8)

Published
Aug 10, 2026
Updated
Oct 21, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-68383

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • ba37807d08bae67de6139346a85650cab5f6145a, 683b0e397dad9f26a42dcacf6f7f545a77ce6c06, 6.17affected
    • b17fcce70733c211cb5dabf54f4f9491920b1d92 and later · before eac2839585741e6c1b4af261a0b58bca0d6f5436affected · git
    • 6bd90e700b4285e6a7541e00f969cab0d696adde and later · before 88c38ff74f8345fcf8852549f94025754019b037affected · git
    • 6bd90e700b4285e6a7541e00f969cab0d696adde and later · before 77fd62412431e8c80ef2ad61466bc76fe425f80aaffected · git
    • 6bd90e700b4285e6a7541e00f969cab0d696adde and later · before 299bc6d50b1bed7d1f408391736712f01a0855e2affected · git
    • 6.12.43 and later · before 6.12.114affected · semver
    • 6.15.11 and later · before 6.16affected · semver
    • 6.16.2 and later · before 6.17affected · semver
    • before 6.17not affected · semver
    • 6.12.114 and later · up to and including 6.12.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.115-26.12.115-2
Debian:14linuxbefore 7.1.6-17.1.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-68381Aug 10, 2026 · ksmbd: pin conn during async oplock break notification
    39Monitor
  • ← EarlierCVE-2026-68382Aug 10, 2026 · drm/xe/guc: Hold device ref until queue teardown completes
    31Monitor
  • Later →CVE-2026-68384Aug 10, 2026 · drm/xe/vf: Fix VF CCS attach/detach race with in-flight BO moves
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux299bc6d50b1bed7d1f408391736712f01a0855e2Vendor (CNA)
Linux Linux6.12.114Vendor (CNA)
Linux Linux6.16Vendor (CNA)
Linux Linux6.17Vendor (CNA)
Linux Linux77fd62412431e8c80ef2ad61466bc76fe425f80aVendor (CNA)
Linux Linux88c38ff74f8345fcf8852549f94025754019b037Vendor (CNA)
Linux Linuxeac2839585741e6c1b4af261a0b58bca0d6f5436Vendor (CNA)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)
debian:linux7.1.6-1 · Debian:14Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()
    39Monitor
  • CVE-2026-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust
    39Monitor
  • CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()
    39Monitor
  • CVE-2026-681560 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update
    39Monitor
  • CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification
    39Monitor
  • CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
    39Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records