CVE-2025-38652
f2fs: fix to avoid out-of-boundary access in devs.path
Reported by linux · Published August 22, 2025
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid out-of-boundary access in devs.path - touch /mnt/f2fs/012345678901234567890123456789012345678901234567890123 - truncate -s $((1024*1024*1024)) \ /mnt/f2fs/012345678901234567890123456789012345678901234567890123 - touch /mnt/f2fs/file - truncate -s $((1024*1024*1024)) /mnt/f2fs/file - mkfs.f2fs /mnt/f2fs/012345678901234567890123456789012345678901234567890123 \ -c /mnt/f2fs/file - mount /mnt/f2fs/012345678901234567890123456789012345678901234567890123 \ /mnt/f2fs/loop [16937.192225] F2FS-fs (loop0): Mount Device [ 0]: /mnt/f2fs/012345678901234567890123456789012345678901234567890123\xff\x01, 511, 0 - 3ffff [16937.192268] F2FS-fs (loop0): Failed to find devices If device path length equals to MAX_PATH_LEN, 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 f2fs_dev_info { ... char path[MAX_PATH_LEN]; ... }; Let's add one byte space for sbi->devs.path[] to store null character of device path string.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | dc0172c74bd9edaee7bea2ebb35f3dbd37a8ae80, 755427093e4294ac111c3f9e40d53f681a0fbdaa, 70849d33130a2cf1d6010069ed200669c8651fbd, 666b7cf6ac9aa074b8319a2b68cba7f2c30023f0, 5661998536af52848cc4d52a377e90368196edea, 1cf1ff15f262e8baf12201b270b6a79f9d119b2d, 1b1efa5f0e878745e94a98022e8edc675a87d78e |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 3c62be17d4f562f43fe1d03b48194399caa35aa5, 3c62be17d4f562f43fe1d03b48194399caa35aa5, 3c62be17d4f562f43fe1d03b48194399caa35aa5 |
| Linux | Linux | 4.10, 0, 5.4.297 |
| Linux | Linux | 3c62be17d4f562f43fe1d03b48194399caa35aa5, 6.12.42, 6.15.10 |
| linux | linux_kernel | 4.10, 4.10, 4.10 |
Timeline
- Aug 22, 2025 CVE Published
- Aug 23, 2025 EPSS Score (30 in total, the first dated here)
- Oct 12, 2025 PoC Published (13 in total, the first dated here)
- Nov 17, 2025 CVE Updated
- Mar 29, 2026 Distribution Patch (174 in total, the first dated here)
- Mar 29, 2026 Security Advisory (222 in total, the first dated here)
- Jun 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-38652
vulnetix vdb fixes CVE-2025-38652
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-38652/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart