ocfs2: reject FITRIM ranges shorter than a cluster
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ aa89762c54800208d5afdcd8e6bf124818f17fe0 · < 3fa7139b5f42731a61f78c42433adae13f9adc21| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: reject FITRIM ranges shorter than a cluster
ocfs2_trim_mainbm() trims the global bitmap in cluster units, but its too-short range validation only checks sb->s_blocksize.
On filesystems with a cluster size larger than the block size, a FITRIM range that is at least one block but shorter than one cluster is accepted and shifted down to len == 0. The later start + len - 1 and len -= ... arithmetic then underflows and can drive trimming past the requested range.
Reject ranges shorter than s_clustersize instead. That preserves the existing -EINVAL behavior for requests that cannot discard even one allocation unit and keeps zero-cluster trims out of the group walk.
From the CVE record · Linux
The Linux kernel’s ocfs2 FITRIM handling accepts a range shorter than one cluster when the cluster size exceeds the block size. A caller able to issue such a FITRIM request can trigger arithmetic underflow that drives trimming past the requested range.
Administrators running Linux systems with ocfs2 filesystems should check whether their kernel includes the fix; affected versions were not provided.