Bug 2521437 (CVE-2026-74596)

Summary: CVE-2026-74596 kernel: fs,fsverity: remove check for fsverity being enabled in setattr_prepare()
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's fsverity subsystem. The vulnerability is due to the removal of a check in the setattr_prepare() function, which previously verified if fs-verity was enabled. This change allows fsverity files to be truncated even when the fs-verity feature is not active on the filesystem. This could lead to unintended modifications of fsverity protected files, potentially impacting data integrity.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-22 15:45:34 UTC
In the Linux kernel, the following vulnerability has been resolved:

fs,fsverity: remove check for fsverity being enabled in setattr_prepare()

The check that fs-verity is available in the kernel is not necessary
here. Filesystems could have fsverity files even without fs-verity
enabled. In that case, truncate on fsverity file will succeed, what this
check is trying to prevent.