Bug 2532471 (CVE-2026-89770) - CVE-2026-89770 kernel: iomap: don't free integrity payload that doesn't exist
Summary: CVE-2026-89770 kernel: iomap: don't free integrity payload that doesn't exist
Keywords:
Status: NEW
Alias: CVE-2026-89770
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-11 23:21 UTC by OSIDB Bzimport
Modified: 2026-09-15 13:57 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-11 23:21:36 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.