CVE-2026-99051
Last modified
CVE-2026-99051 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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..
Description
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= f77f281b61183a5c0b87e6a4d101c70bd32c1c79, < fa84f091a8e7fc46fd29834496fab9739dd4c8dc; >= f77f281b61183a5c0b87e6a4d101c70bd32c1c79, < e58c3805ed325fe2d4ae2dd467c0486cc860b733 |
| Linux | Linux | 7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-99051?
How severe is CVE-2026-99051?
How do I fix CVE-2026-99051?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-99046In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-99047In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99048In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99049In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9905Use after free in Accessibility in Google Chrome on Windows …8.3
- CVE-2026-99050In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-99052In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99053In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-99054In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-99055In the Linux kernel, the following vulnerability has been re…
- CVE-2026-99056In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-99057In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-99051?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
