iomap: don't free integrity payload that doesn't exist
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 65651f1001aa3638909bc58c7b2b46160692757b and Kernel 8a8685b32c0718cc7b2cb4d6202e5a5b8e0a8e2d.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.1, >=0b10a370529cbd7b918c1eef43d409e43d9e0b78 <65651f1001aa3638909bc58c7b2b46160692757b, >=0b10a370529cbd7b918c1eef43d409e43d9e0b78 <8a8685b32c0718cc7b2cb4d6202e5a5b8e0a8e2d | 65651f1001aa3638909bc58c7b2b46160692757b, 8a8685b32c0718cc7b2cb4d6202e5a5b8e0a8e2d |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket