# CVE-2026-74606: eventfs: Fix use-after-free in eventfs_remove_rec()

> A use-after-free in the Linux kernel eventfs allows attackers to potentially execute code or escalate privileges via recursive removal logic.

- **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:** 22 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** BELL-CVE-2026-74606, DEBIAN-CVE-2026-74606, GHSA-qfq9-8c5m-346x, UBUNTU-CVE-2026-74606

## What is CVE-2026-74606?

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

eventfs: Fix use-after-free in eventfs_remove_rec()

eventfs_remove_rec() recursively removes the child at the current loop
position. After the recursive call returns, list_for_each_entry() advances
by reading list.next from the removed child.

If free_ei() drops the final reference, release_ei() reuses the list/rcu
union to queue an SRCU callback. The child may be freed before that read.
The eventfs_mutex serializes list updates, but it does not keep the removed
child alive or prevent the SRCU callback from running.

Use list_for_each_entry_safe() to save the next sibling before recursively
removing the current child.

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


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

Apply the vendor's patch.

## Is CVE-2026-74606 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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