Bug 2576958 (CVE-2026-99407)

Summary: CVE-2026-99407 kernel: kernel: File system corruption via invalid XFS summary counter repair
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: unspecifiedKeywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the Linux kernel's XFS file system. During file system scrub and repair operations, the kernel fails to mark a scan as incomplete when invalid summary counter values are encountered. Consequently, a local user with permissions to invoke file system repair could cause corrupted summary values to be written to disk, resulting in file system corruption and potential Denial of Service (DoS).
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-11-19 15:42:32 UTC
In the Linux kernel, the following vulnerability has been resolved:

xfs: don't repair fs summary counters with garbage

LOLLM noticed that if we scan the filesystem and come up with totally
garbage numbers for the summary counters, we don't actually mark the
scan incomplete.  Because we don't do this, repair can install the
garbage values into the filesystem, making things worse.  Don't do that.