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.

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.

The vulnerability is a classic use‑after‑free in the kernel, implying a high severity if exploited. No CVSS score is provided, and the EPSS score is unavailable, but the absence of a KEV listing does not eliminate the risk. The likely attack vector is local; an attacker with the ability to trigger fsverity lookups or removals could potentially achieve privilege escalation or arbitrary code execution within the kernel context.