# CVE-2026-80713: io_uring: preserve task restrictions across exec

> Attackers can bypass io_uring task restrictions after exec, potentially escalating privileges by creating unrestricted rings.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N`)
- **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:** 28 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-80713, GHSA-jh6f-w2gp-43jq, UBUNTU-CVE-2026-80713

## What is CVE-2026-80713?

CVE-2026-80713 is a high-severity vulnerability in Linux, published on 28 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:

io_uring: preserve task restrictions across exec

Per-task restrictions apply to all rings created by a task. Once
installed, they should not be dropped across exec.

For a task that has used io_uring, the exec cancellation path calls
__io_uring_free(). This frees both the task context and the per-task
restriction, so a ring created after exec is unrestricted.

Split task context cleanup into io_uring_free_tctx(), and use it from
the exec cancellation path. Keep __io_uring_free() for final task
cleanup, where both the context and restriction are released.

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


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

Apply the vendor's patch.

## Is CVE-2026-80713 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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