In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid out-of-boundary access in devs.path
[16937.192268] F2FS-fs (loop0): Failed to find devices
If device path length equals to MAXPATHLEN, sbi->devs.path[] may not end up w/ null character due to path array is fully filled, So accidently, fields locate after path[] may be treated as part of device path, result in parsing wrong device path.
struct f2fsdevinfo { ... char path[MAXPATHLEN]; ... };
Let's add one byte space for sbi->devs.path[] to store null character of device path string.
{
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38652.json"
}"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38652.json"
[
{
"signature_type": "Line",
"source": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git@5661998536af52848cc4d52a377e90368196edea",
"id": "CVE-2025-38652-5046d74a",
"deprecated": false,
"target": {
"file": "fs/f2fs/f2fs.h"
},
"signature_version": "v1",
"digest": {
"line_hashes": [
"168390798327985228669560338565098265597",
"9507932505574746405002199272594869054",
"326441455551603201391041850838023154343",
"335803760321613655662100127686103288981"
],
"threshold": 0.9
}
}
]