# CVE-2026-68313: tipc: fix infinite loop in __tipc_nl_compat_dumpit

> A local attacker can trigger an infinite loop in the TIPC subsystem, causing a denial of service by starving other tasks waiting on the mutex.

- **Severity:** Not scored
- **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:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68313, DEBIAN-CVE-2026-68313, GHSA-vpjw-59q8-958p, UBUNTU-CVE-2026-68313

## What is CVE-2026-68313?

CVE-2026-68313 is a denial of service 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:

tipc: fix infinite loop in __tipc_nl_compat_dumpit

cmd->dumpit callback can return a negative errno, causing an infinite
loop due to the while(len) condition. As the loop never terminates,
genl_mutex is never released, and other tasks waiting on it starve in D
state.

Check dumpit's return value, propagate it and jump to err_out on error.

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


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

Apply the vendor's patch.

## Is CVE-2026-68313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68313 is a denial of service 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-68313 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-68313/ (Markdown: https://insights.sbomify.com/CVE-2026-68313/index.md)
```

## Sources

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

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