PT-2024-28093

CVE-2024-38636

·

Published

2024-03-27

·

Updated

2025-02-03

Description by

CVSS 3.1
5.5
Medium
MetricsAV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Name of the Vulnerable Software and Affected Versions Linux kernel versions prior to 6.6.37
Description The issue arises when the multi-devices feature is enabled in the Linux kernel, specifically with the f2fs file system. In this scenario, the f2fs map blocks() function may return a zero block address in non-primary devices, which is a valid block address. However, the f2fs iomap begin() function treats this as an invalid block address, triggering a warning in the iomap framework code. This warning is caught during the zbd/010 test, which checks for gap zone support with F2FS. The root cause of the issue is the incorrect assumption in f2fs iomap begin() about the physical block address of the whole f2fs file system. To fix this issue, a more direct approach is used, checking the (map.m flags & F2FS MAP MAPPED) condition instead of (map.m pblk != NULL ADDR).
Recommendations To resolve this issue, update the Linux kernel to version 6.6.37 or later. As a temporary workaround, consider disabling the multi-devices feature in the f2fs file system until the update can be applied.
Exploitability
Exploit
Fix
Impacts
Researchers
Vendors
Affected products
Related identifiers
MGASA-2024-0263
MGASA-2024-0266
OESA-2024-1766
SUSE-SU-2024:2571-1
SUSE-SU-2024:2896-1
SUSE-SU-2024:2973-1
SUSE-SU-2025:20008-1
SUSE-SU-2025:20028-1
USN-6999-1
USN-6999-2
USN-7004-1
USN-7005-1
USN-7005-2
USN-7008-1
USN-7029-1
Found an issue in the description? Have something to add? Feel free to write us 👾