Description
In the Linux kernel, the following vulnerability has been resolved: iomap: don't free integrity payload that doesn't exist fs_bio_integrity_alloc might not allocate a bio integrity payload if PI verification is disabled on the block device. Check for that case before calling fs_bio_integrity_free in iomap_bio_read_folio_range_sync to avoid a NULL pointer dereferences. Make the branch cover the PI verification as well - while fs_bio_integrity_verify works without an integrity payload, it requires one to actually do useful work.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
0b10a370529cbd7b918c1eef43d409e43d9e0b78 to < 65651f1001aa3638909bc58c7b2b46160692757baffected0b10a370529cbd7b918c1eef43d409e43d9e0b78 to < 8a8685b32c0718cc7b2cb4d6202e5a5b8e0a8e2daffected
Linux Linux
Default version status: affected
7.1affected0 to < 7.1unaffected7.2.4 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected