iomap: don't free integrity payload that doesn't exist
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s iomap code can dereference a NULL pointer when reading a folio if PI verification is disabled on the block device and no bio integrity payload was allocated. The input does not specify whether an attacker can trigger this, or any required access or user interaction.
Engineers running Linux kernels should check whether their kernel includes the iomap fix; affected versions are not specified.