f2fs: protect extension_list reading with sb_lock in f2fs_sbi_show()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b6a06cbbb5f7fd03589cff9178314af04c568826 · < 5909bedbed38c558bee7cb6758ceedf9bc3a9194| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
f2fs: protect extension_list reading with sb_lock in f2fs_sbi_show()
In f2fs_sbi_show(), the extension_list, extension_count and hot_ext_count are read without holding sbi->sb_lock. If a concurrent sysfs store modifies the extension list via f2fs_update_extension_list(), the show path may read inconsistent count and array contents, potentially leading to out-of-bounds access or displaying stale data.
Fix this by holding sb_lock around the entire extension list read and format operation.
From the CVE record · Linux
The Linux kernel’s f2fs_sbi_show() reads the extension list without holding sb_lock. If a concurrent sysfs store changes the list, the read may access data out of bounds or display stale data. The input does not specify authentication requirements.
Engineers running Linux kernels with f2fs should check their exposure; affected versions are not specified.