f2fs: fix KMSAN uninit-value in extent_info usage
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 94afd6d6e5253179c9b891d02081cc8355a11768 · < 01b6f5955e0008af6bc3a181310d2744bb349800| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix KMSAN uninit-value in extent_info usage
KMSAN reported a use of uninitialized value in `__is_extent_mergeable()` and `__is_back_mergeable()` via the read extent tree path.
The root cause is that `get_read_extent_info()` only initializes three fields (`fofs`, `blk`, `len`) of `struct extent_info`, leaving the remaining fields uninitialized. This leads to undefined behavior when those fields are accessed later, especially during extent merging.
Fix it by zero-initializing the `extent_info` struct before population.
From the CVE record · Linux
The Linux kernel’s f2fs read extent tree path can use uninitialized fields during extent merging, causing undefined behavior. The input does not specify what an attacker could achieve or the access, authentication, or user-interaction conditions required.
Engineers running Linux kernels with f2fs should check their versions; affected versions were not provided.