In the Linux kernel, the following vulnerability has been resolved: fsverity: RCU-delay the freeing of struct fsverity_info __fsverity_…
CVE-2026-99051 · GHSA-7hq4-c7jg-2h9h · EUVD-2026-108846 · published 23 Oct 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-99051?
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: patch: 7.3
- Linux Linux: 7.0
- Linux Linux: f77f281b61183a5c0b87e6a4d101c70bd32c1c79 <e58c3805ed325fe2d4ae2dd467c0486cc860b733
- Linux Linux: patch: 0
- Linux Linux: f77f281b61183a5c0b87e6a4d101c70bd32c1c79 <fa84f091a8e7fc46fd29834496fab9739dd4c8dc
- Linux Linux: patch: 7.2.11
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:
fsverity: RCU-delay the freeing of struct fsverity_info
__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses
rcu_read_lock() and doesn't directly synchronize with
fsverity_remove_info().
For the same inode this isn't a problem: its fsverity_info is removed
only at inode eviction time or upon failure to enable verity, when the
inode no longer needs its fsverity_info and it will no longer be
accessed via that inode.
However, this is broken and can cause a use-after-free for concurrent
__fsverity_get_info() for *different* inodes. Those rely on following
fsverity_info::rhash_head in the rhashtable under rcu_read_lock() only.
They also use fsverity_info::inode to do the key comparison.
Fix this by RCU-delaying the freeing of 'struct fsverity_info' after
it's been removed from the rhashtable.
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/fa84f091a8e7fc46fd29834496fab9739dd4c8dc
- git.kernel.org/stable/c/e58c3805ed325fe2d4ae2dd467c0486cc860b733
- nvd.nist.gov/vuln/detail/CVE-2026-99051
Merged from ENISA EUVD. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON