# CVE-2026-80860: fuse: fix race between interrupt and resend

> A race condition in the Linux kernel FUSE subsystem can trigger a kernel warning and potential denial of service.

- **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:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-80860, DEBIAN-CVE-2026-80860, GHSA-8279-rm4w-j7mp, UBUNTU-CVE-2026-80860

## What is CVE-2026-80860?

CVE-2026-80860 is a vulnerability in Linux, published on 4 Sep 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:

fuse: fix race between interrupt and resend

After commit f8fce75fedf7 ("fuse: clear intr_entry in fuse_resend and
fuse_remove_pending_req") the WARN_ON(!list_empty(&req->intr_entry)) in
fuse_request_free() still triggers due to the following race:

In request_wait_answer()
  if (test_bit(FR_SENT, &req->flags)) -> returns true

In fuse_chan_resend()
  clear_bit(FR_SENT, &req->flags)

In request_wait_answer()
  queue_interrupt(req)

Fix by:

 - move clearing FR_SENT inside fpq->lock

 - move setting FR_PENDING inside fiq->lock

 - recheck FR_SENT after acquiring fiq->lock in fuse_dev_queue_interrupt()

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


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

Apply the vendor's patch.

## Is CVE-2026-80860 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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