A flaw in the Linux kernel SMB client implementation allows for improper handling of fallocate requests, which could lead to data integrity issues and potential system instability.

The vulnerability exists in the smb3_simple_fallocate_range function, where the kernel incorrectly calculates file ranges when processing server responses. This oversight results in skipped holes in the file system not being zero-filled, which violates file allocation expectations and can cause subsequent write operations to fail.

The improper handling of file allocation ranges poses a significant risk to data integrity for systems utilizing SMB mounts. Because the kernel fails to correctly zero-fill unallocated space, applications may experience unexpected write failures, leading to service downtime or potential data corruption. Given the CVSS score of 9.8, this flaw is considered critical, as it directly impacts the stability and reliability of storage operations across affected infrastructure.

Immediate Action: Update the Linux kernel to version 5.10.265, 5.15.216, 6.1.183, 6.6.148, or a later stable release provided by your distribution vendor.

Proactive Monitoring: Monitor system logs for kernel-level errors related to SMB or fallocate operations, particularly those indicating space allocation failures or unexpected I/O errors.

Compensating Controls: If immediate patching is not feasible, restrict the use of SMB shares for critical application data storage or implement filesystem-level quotas to mitigate the impact of write failures.

Public Exploit Available: Unknown.

The critical nature of this kernel vulnerability necessitates immediate attention, particularly for environments heavily reliant on SMB network file sharing. Organizations should prioritize the deployment of the provided kernel patches across all affected server and workstation fleets to prevent potential data integrity incidents. Testing should be conducted in a staging environment to ensure compatibility before broad deployment.