6 matches found
CVE-2026-99575
In the Linux kernel, the following vulnerability has been resolved: f2fs: return -EIO for a lost inode block after cperror After cperror, dirty node caches are dropped without being written. If such an inode was never written, its NAT entry is still NEWADDR, and reading its inode block returns...
CVE-2026-99575 f2fs: return -EIO for a lost inode block after cp_error
In the Linux kernel, the following vulnerability has been resolved: f2fs: return -EIO for a lost inode block after cperror After cperror, dirty node caches are dropped without being written. If such an inode was never written, its NAT entry is still NEWADDR, and reading its inode block returns...
CVE-2026-99575 f2fs: return -EIO for a lost inode block after cp_error
In the Linux kernel, the following vulnerability has been resolved: f2fs: return -EIO for a lost inode block after cperror After cperror, dirty node caches are dropped without being written. If such an inode was never written, its NAT entry is still NEWADDR, and reading its inode block returns...
EUVD-2026-131025
In the Linux kernel, the following vulnerability has been resolved: f2fs: return -EIO for a lost inode block after cperror After cperror, dirty node caches are dropped without being written. If such an inode was never written, its NAT entry is still NEWADDR, and reading its inode block returns...
CVE-2026-99575
The Linux kernel f2fs file system contains a vulnerability where missing inode blocks after a cp_error or shutdown return -ENOENT instead of -EIO. Because f2fs_get_dnode_of_data() passes this error upward, callers interpret it as a hole. This causes fiemap to walk block by block up to maxbytes (a...
CVE-2026-99575: Linux: In the Linux kernel, the following vulnerability has been resolved: f2fs: return -EIO for a lost inode block after…
In the Linux kernel, the following vulnerability has been resolved: f2fs: return -EIO for a lost inode block after cperror After cperror, dirty node caches are dropped without being written. If such an inode was never written, its NAT entry is still NEWADDR, and reading its inode block returns...