AZL-115375: CVE-2026-99607 affecting package kernel 6.6.161.1-1
In the Linux kernel, the following vulnerability has been resolved:
ext2: preserve IOMAPFDIRTY for extending direct writes
ext2iomapbegin() sets IOMAPFDIRTY for writes that may extend isize, but clears the flag after ext2getblocks(). When the write uses an existing mapped block, iomap can then use FUA and skip genericwritesync(), even though ext2diowriteendio() updates the inode size. An ODSYNC write can therefore return without persisting the new size.
For example, on a FUA-capable device, a 512-byte ODIRECT|ODSYNC write at offset 512 into a fsynced one-byte file returns successfully and extends the in-memory size to 1024, while an immediate read of the on-disk inode still shows size 1. An explicit fsync persists the new size.
Move setting of IOMAPFDIRTY after the initialization.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Operational
Call explicit fsync after the write to persist the new size.