{"id":"AZL-115303","summary":"CVE-2026-99575 affecting package kernel 6.6.161.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: return -EIO for a lost inode block after cp_error\n\nAfter cp_error, dirty node caches are dropped without being written.\nIf such an inode was never written, its NAT entry is still NEW_ADDR,\nand reading its inode block returns -ENOENT.\n\nf2fs_get_dnode_of_data() passes that -ENOENT up, and callers take it\nas a hole. Since the inode block is missing, the next offset can only\nadvance one block, so fiemap walks block by block up to maxbytes,\nabout 2^30 blocks, while holding the inode lock. It took hours in a\npower-off recovery test after shutdown and blocked unlink and umount\non the file.\n\nReturn -EIO instead of -ENOENT when the inode block itself is missing\nafter cp_error or shutdown. A missing direct or indirect node is still\nreported as -ENOENT.","modified":"2026-11-21T14:17:23.619000501Z","published":"2026-11-20T06:17:48Z","upstream":["CVE-2026-99575"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99575"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.161.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-115303.json"}}],"schema_version":"1.9.2"}