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.
Published: 2026-09-11
Score: 4.7 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service
Action: Immediate Patch
AI Analysis

Impact

In the Linux kernel’s iomap subsystem, a null pointer dereference occurs when the code attempts to free an integrity payload that was never allocated because block device PI verification is disabled. This flaw can crash the kernel during of service. The weakness is an improper null check classified as CWE‑476.

Affected Systems

All Linux kernel builds that lack the corrective commit patch are vulnerable, covering every distribution that ships an unpatched kernel version. Specific version ranges are not enumerated in the advisory, so any kernel not containing the fix should be considered exposed.

Risk and Exploitability

Based on the description, it is inferred that the vulnerability is exploitable locally by triggering a sync read on a block device configured with PI verification 4.7 reflects moderate severity, and the EPSS score of <1% indicates a low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog, suggesting no known active attacks. loss of system availability.

Generated by OpenCVE AI on September 15, 2026 at 19:15 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernele.g., 65651f1001aa3638909bc58c7b2b46160692757b) that removes the harmful free call.
  • If an immediate kernel upgrade is not possible, temporarily disable PI verification on the affected block devices to prevent the null dereference during sync read operations.
  • Continuously monitor system logs for kernel panics related to iomap read operations and plan a timely kernel upgrade as soon as compatibility allows.

Generated by OpenCVE AI on September 15, 2026 at 19:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 12 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Sat, 12 Sep 2026 10:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476

Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
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.
Title iomap: don't free integrity payload that doesn't exist
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-11T19:47:09.630Z

Reserved: 2026-09-11T19:38:34.765Z

Link: CVE-2026-89770

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-11T20:20:08.353

Modified: 2026-09-11T20:20:08.353

Link: CVE-2026-89770

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-11T19:47:09Z

Links: CVE-2026-89770 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-15T19:30:12Z

Weaknesses