AZL-115375: CVE-2026-99607 affecting package kernel 6.6.161.1-1

Published Nov 20, 2026
·
Updated

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

1 affected component
azure-linux/kernel<=6.6.161.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Operational

    Call explicit fsync after the write to persist the new size.

Event History

Nov 20, 2026
Advisory Published
via OSV·06:17 AM
Data Sourced
via OSV·06:17 AM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203