# CVE-2026-64517: drm/xe/gsc: Fix double-free of managed BO in error path

> A double-free vulnerability in the Linux kernel's Intel Xe graphics driver allows local attackers to cause a system crash or potentially execute arbitrary code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 25 Jul 2026
- **Also known as:** BELL-CVE-2026-64517, DEBIAN-CVE-2026-64517, GHSA-hw28-fxfq-92xc, ROOT-OS-UBUNTU-2204-CVE-2026-64517, UBUNTU-CVE-2026-64517

## What is CVE-2026-64517?

CVE-2026-64517 is an use after free vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

drm/xe/gsc: Fix double-free of managed BO in error path

The error path in xe_gsc_init_post_hwconfig() explicitly frees a BO
allocated with xe_managed_bo_create_pin_map() via
xe_bo_unpin_map_no_vm(). Since the managed BO already has a devm
cleanup action registered, this causes a double-free when devm
unwinds during probe failure.

Remove the explicit free and let devm handle it, consistent with
all other xe_managed_bo_create_pin_map() callers.

(cherry picked from commit 71d61e3e299a17139e47f980a4d6f425b2c59bf7)

## Which versions are affected by CVE-2026-64517?


## How do I fix CVE-2026-64517?

Apply the vendor's patch.

## Is CVE-2026-64517 being exploited?

There is no known exploitation of CVE-2026-64517 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64517 and fix it if it is affected.

What it is: CVE-2026-64517 is an use after free vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64517 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64517/ (Markdown: https://insights.sbomify.com/CVE-2026-64517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64517
- OSV: https://osv.dev/vulnerability/CVE-2026-64517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64517/
Summaries are generated and may contain mistakes; the official description above is the record.