{"id":"AZL-115375","summary":"CVE-2026-99607 affecting package kernel 6.6.161.1-1","details":"In the Linux kernel, the following vulnerability has been resolved:\n\next2: preserve IOMAP_F_DIRTY for extending direct writes\n\next2_iomap_begin() sets IOMAP_F_DIRTY for writes that may extend i_size,\nbut clears the flag after ext2_get_blocks(). When the write uses an\nexisting mapped block, iomap can then use FUA and skip\ngeneric_write_sync(), even though ext2_dio_write_end_io() updates the\ninode size. An O_DSYNC write can therefore return without persisting\nthe new size.\n\nFor example, on a FUA-capable device, a 512-byte O_DIRECT|O_DSYNC write\nat offset 512 into a fsynced one-byte file returns successfully and\nextends the in-memory size to 1024, while an immediate read of the\non-disk inode still shows size 1. An explicit fsync persists the new\nsize.\n\nMove setting of IOMAP_F_DIRTY after the initialization.","modified":"2026-11-21T14:17:23.608600630Z","published":"2026-11-20T06:17:52Z","upstream":["CVE-2026-99607"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99607"}],"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-115375.json"}}],"schema_version":"1.9.2"}