CVE-2026-89770: iomap: don't free integrity payload that doesn't exist
In the Linux kernel, the following vulnerability has been resolved:
iomap: don't free integrity payload that doesn't exist
fsbiointegrityalloc might not allocate a bio integrity payload if PI verification is disabled on the block device. Check for that case before calling fsbiointegrityfree in iomapbioreadfoliorangesync to avoid a NULL pointer dereferences.
Make the branch cover the PI verification as well - while fsbiointegrityverify works without an integrity payload, it requires one to actually do useful work.
Event History
Frequently Asked Questions
What storage-integrity configuration is associated with the failure condition?
The failure can occur when PI verification is disabled on the block device, because integrity-payload allocation may then produce no payload. The affected read path must avoid freeing or relying on that absent payload.
Can integrity verification still provide meaningful verification without an integrity payload?
No. The verification function can run without an integrity payload, but it requires a payload to perform useful verification work.