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.
Published: 2026-10-23
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: Use‑After‑Free Leading to Arbitrary Code Execution
Action: Patch Immediately
AI Analysis

Impact

A race condition in the Linux kernel’s fsverity subsystem allows a concurrent __fsverity_get_info() call to access a freed fsverity_info structure. This use‑after‑free occurs when different inodes are processed, potentially allowing an attacker to manipulate kernel memory or execute arbitrary code after the structure is released.

Affected Systems

All Linux kernel installations that include fsverity support and have not applied the RCU‑delay patch are affected. The precise kernel versions that lack the fix are not disclosed, but the issue exists in any kernel build where the mentioned race condition is present.

Risk and Exploitability

The vulnerability is a classic use‑after‑free in the kernel, with a CVSS score of 7.8 indicating a high-to-moderate severity. The EPSS score is less than 1%, and the vulnerability is not listed in CISA’s KEV catalog, which does not negate the risk of exploitation. The likely attack vector is local; an attacker that can trigger fsverity lookups or removals may achieve privilege escalation or arbitrary kernel code execution.

Generated by OpenCVE AI on October 27, 2026 at 13:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a Linux kernel update that includes the RCU‑delay fix for fsverity_info, typically available in recent mainline releases.
  • If a timely kernel update is not possible, obtain and apply the backported patch that delays freeing of struct fsverity_info from the kernel mailing list or Git repository to close the race condition.
  • As a temporary measure, disable fsverity support (CONFIG_FS_VERITY) in the kernel configuration or unload any verity modules if they are not required, accepting the loss of integrity verification for the affected filesystems.

Generated by OpenCVE AI on October 27, 2026 at 13:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-9018-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-9018-2 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-9019-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-9020-1 Linux kernel vulnerabilities
History

Tue, 27 Oct 2026 12:30:00 +0000


Sat, 24 Oct 2026 14:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Sat, 24 Oct 2026 00:45:00 +0000

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux

Fri, 23 Oct 2026 16:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416

Fri, 23 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
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.
Title fsverity: RCU-delay the freeing of struct fsverity_info
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-24T14:10:12.469Z

Reserved: 2026-09-25T10:25:14.388Z

Link: CVE-2026-99051

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-23T13:17:28.633

Modified: 2026-10-24T14:16:53.773

Link: CVE-2026-99051

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-23T00:00:00Z

Links: CVE-2026-99051 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-27T14:00:05Z

Weaknesses