https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 26 Oct 2026 14:20:26 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-99051 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fsverity: RCU-delay the freeing of struct fsverity_info</p> <p>__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses rcu_read_lock() and doesn&#39;t directly synchronize with fsverity_remove_info().</p> <p>For the same inode this isn&#39;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.</p> <p>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.</p> <p>Fix this by RCU-delaying the freeing of &#39;struct fsverity_info&#39; after it&#39;s been removed from the rhashtable.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fsverity: RCU-delay the freeing of struct fsverity_info</p> <p>__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses rcu_read_lock() and doesn&#39;t directly synchronize with fsverity_remove_info().</p> <p>For the same inode this isn&#39;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.</p> <p>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.</p> <p>Fix this by RCU-delaying the freeing of &#39;struct fsverity_info&#39; after it&#39;s been removed from the rhashtable.</p> https://db.gcve.eu/vuln/fkie_cve-2026-99051 https://db.gcve.eu/vuln/ghsa-7hq4-c7jg-2h9h <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fsverity: RCU-delay the freeing of struct fsverity_info</p> <p>__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses rcu_read_lock() and doesn&#39;t directly synchronize with fsverity_remove_info().</p> <p>For the same inode this isn&#39;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.</p> <p>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.</p> <p>Fix this by RCU-delaying the freeing of &#39;struct fsverity_info&#39; after it&#39;s been removed from the rhashtable.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fsverity: RCU-delay the freeing of struct fsverity_info</p> <p>__fsverity_get_info() calls rhashtable_lookup_fast(), which just uses rcu_read_lock() and doesn&#39;t directly synchronize with fsverity_remove_info().</p> <p>For the same inode this isn&#39;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.</p> <p>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.</p> <p>Fix this by RCU-delaying the freeing of &#39;struct fsverity_info&#39; after it&#39;s been removed from the rhashtable.</p> https://db.gcve.eu/vuln/ghsa-7hq4-c7jg-2h9h