eventfs: Use children field for rcu head and add memory barriers
CVE-2026-74605 · published 22 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-74605?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: f3f41f444b321ec393edbc251e024fd62658ce55 to < 25d27d5fa8645ab61018c3efec5c69f49280ca7d, 704f960dbee2f1634f4b4e16f208cb16eaf41c1e to < 1b95382da85cff3bf0f922ff0275f186abdadfce, 704f960dbee2f1634f4b4e16f208cb16eaf41c1e to < 2b80707b9e27671e10840d17c6f8f774c4ad9847, 704f960dbee2f1634f4b4e16f208cb16eaf41c1e to < 004f7232e49730448f91665e76bdd7dff8e0c638
- Linux Linux: 6.8
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
eventfs: Use children field for rcu head and add memory barriers
When an eventfs inode is freed, it sets ei->is_freed and then uses its
ei->list to add it to the srcu link list as the list field is a union with
the rcu list head. As the ei->list is used to iterate over an SRCU
protected list without taking the eventfs_mutex, there's nothing stopping
the iteration over that list to see the ei->rcu instead of the ei->list
and it will read a corrupt target.
To fix this, change the union of the rcu list head with the children list.
On freeing the eventfs inode, set the is_free and execute a smp_wmb()
before adding the eventfs inode to the SRCU list.
On iteration of the ei->children list, at the start, execute a smp_rmb()
and then read the is_freed of the ei to see if the children list is still
valid. If is_freed is set, then the ei_child read is not valid and the
loop should exit immediately.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/25d27d5fa8645ab61018c3efec5c69f49280ca7d
- git.kernel.org/stable/c/1b95382da85cff3bf0f922ff0275f186abdadfce
- git.kernel.org/stable/c/2b80707b9e27671e10840d17c6f8f774c4ad9847
- git.kernel.org/stable/c/004f7232e49730448f91665e76bdd7dff8e0c638
- git.kernel.org/stable/c/f0ece16ffca7384787b692431961ce202907acf5
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON