CVE-2025-38652

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix to avoid out-of-boundary access in devs.path<br /> <br /> - touch /mnt/f2fs/012345678901234567890123456789012345678901234567890123<br /> - truncate -s $((1024*1024*1024)) \<br /> /mnt/f2fs/012345678901234567890123456789012345678901234567890123<br /> - touch /mnt/f2fs/file<br /> - truncate -s $((1024*1024*1024)) /mnt/f2fs/file<br /> - mkfs.f2fs /mnt/f2fs/012345678901234567890123456789012345678901234567890123 \<br /> -c /mnt/f2fs/file<br /> - mount /mnt/f2fs/012345678901234567890123456789012345678901234567890123 \<br /> /mnt/f2fs/loop<br /> <br /> [16937.192225] F2FS-fs (loop0): Mount Device [ 0]: /mnt/f2fs/012345678901234567890123456789012345678901234567890123\xff\x01, 511, 0 - 3ffff<br /> [16937.192268] F2FS-fs (loop0): Failed to find devices<br /> <br /> If device path length equals to MAX_PATH_LEN, sbi-&gt;devs.path[] may<br /> not end up w/ null character due to path array is fully filled, So<br /> accidently, fields locate after path[] may be treated as part of<br /> device path, result in parsing wrong device path.<br /> <br /> struct f2fs_dev_info {<br /> ...<br /> char path[MAX_PATH_LEN];<br /> ...<br /> };<br /> <br /> Let&amp;#39;s add one byte space for sbi-&gt;devs.path[] to store null<br /> character of device path string.