In the Linux kernel, the f2fs_sbi_show() routine reads critical data structures such as extension_list, extension_count, and hot_ext_count without holding the sb_lock. A concurrent modification via f2fs_update_extension_list() can produce an inconsistent state that may lead to an out-of-bounds read or stale data being displayed. The vulnerability is essentially an unsynchronized race condition that could expose kernel memory contents or trigger a crash due to an out-of-range access.

Any Linux kernel that includes the f2fs file system and has not been updated to the fix is affected. The description does not specify kernel version ranges, implying that every build prior to the patch containing the unguarded read is susceptible, including upstream releases and downstream distributions with the same code.

The CVSS score is not supplied, and the EPSS score is unavailable, so the quantitative severity and exploitation likelihood cannot be determined. The race requires a process that can write to the f2fs sysfs extension list interface; this normally implies local privileged or root access unless the interface is exposed to unprivileged users. The potential out-of-bounds read could expose sensitive kernel data or cause a kernel stop, i.e., a denial of service. The vulnerability is not listed in CISA KEV, suggesting no widespread exploitation has been observed yet.