# CVE-2026-68380: accel/amdxdna: Fix use-after-free of mm_struct in job scheduler

> A use-after-free vulnerability in the Linux kernel's amdxdna driver allows attackers to potentially execute code or escalate privileges via job scheduling.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68380, DEBIAN-CVE-2026-68380, GHSA-q88g-f4fr-ffwf, UBUNTU-CVE-2026-68380

## What is CVE-2026-68380?

CVE-2026-68380 is a high-severity use after free vulnerability in Linux, published on 10 Aug 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:

accel/amdxdna: Fix use-after-free of mm_struct in job scheduler

amdxdna_cmd_submit() stores current->mm in job->mm without holding any
reference. aie2_sched_job_run() later access job->mm from the DRM
scheduler worker thread. With only a raw pointer and no structural
reference, the mm_struct can be freed before the scheduler runs the job.

Fix this by calling mmgrab() to hold a structural mm_count reference for
the lifetime of the job, paired with mmdrop() in every cleanup path.

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


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

Apply the vendor's patch.

## Is CVE-2026-68380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68380 is a high-severity use after free vulnerability in Linux, published on 10 Aug 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-68380 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-68380/ (Markdown: https://insights.sbomify.com/CVE-2026-68380/index.md)
```

## Sources

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

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