In the Linux kernel, the following vulnerability has been resolved: f2fs: explicitly null-terminate the xattr list When setting an xattr, explicitly null-terminate the xattr list. This eliminates the fragile assumption that the unused xattr space is always zeroed. https://git.kernel.org/stable/c/12cf91e23b126718a96b914f949f2cdfeadc7b2a https://git.kernel.org/stable/c/16ae3132ff7746894894927c1892493693b89135 https://git.kernel.org/stable/c/2525d1ba225b5c167162fa344013c408e8b4de36 https://git.kernel.org/stable/c/32a6cfc67675ee96fe107aeed5af9776fec63f11 https://git.kernel.org/stable/c/3e47740091b05ac8d7836a33afd8646b6863ca52 https://git.kernel.org/stable/c/5de9e9dd1828db9b8b962f7ca42548bd596deb8a https://git.kernel.org/stable/c/e26b6d39270f5eab0087453d9b544189a38c8564 https://git.kernel.org/stable/c/f6c30bfe5a49bc38cae985083a11016800708fea
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2265268]
We don't build or ship F2FS in RHEL8 or RHEL8.
This was fixed for Fedora with the 6.6.13 stable kernel updates.
In reply to comment #3: > We don't build or ship F2FS in RHEL8 or RHEL8. Right, the # CONFIG_F2FS_FS is not set
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52436 is: SKIP No affected files built, so skip this CVE NO - - unknown (where first YES/NO value means if related sources built).