Skip to main content
← All vulnerabilities
CVE-2026-89778

isofs: fix out-of-bounds page array access on empty zisofs block

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, and 1 more
None on Exploit-DB, Metasploit or GitHub

Summary

The Linux kernel's ISO 9660 filesystem driver (isofs), specifically its zisofs support for reading compressed files, is affected. A specially crafted disk image mounted with a malformed block-size setting can cause an out-of-bounds memory access during an ordinary file read, which may crash the system or otherwise compromise kernel memory integrity.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

In the Linux kernel, the following vulnerability has been resolved: isofs: fix out-of-bounds page array access on empty zisofs block zisofs_uncompress_block()'s empty-block fast path returns pcount << PAGE_SHIFT, ignoring the incoming poffset, unlike the decompression path which returns bytes produced relative to poffset. zisofs_fill_pages() uses that return to advance its page cursor, so when the zisofs block size is below PAGE_SIZE and a sub-page block leaves poffset partway into a page, a following empty block over-counts and advances pages[] one element past its end, after which "if (poffset && *pages)" reads pages[1] out of bounds. rock.c only rejects a block-size shift > 17, so a crafted "ZF" Rock Ridge record can set it below PAGE_SHIFT; the bug is reached by an ordinary read() of a compressed file on such a mounted ISO9660 image. Return the byte count relative to poffset and zero only [poffset, PAGE_SIZE) of the first page, matching the decompression path. The page-aligned case (poffset == 0) is unaffected. BUG: KASAN: slab-out-of-bounds in zisofs_read_folio (fs/isofs/compress.c:290) Read of size 8 at addr ffff88800f5eac48 by task exploit/142 zisofs_read_folio (fs/isofs/compress.c:290) read_pages (mm/readahead.c:184) ... filemap_read (mm/filemap.c:2814) vfs_read (fs/read_write.c:574) __x64_sys_pread64 (fs/read_write.c:769) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) The buggy address is located 0 bytes to the right of the allocated 8-byte region in the kmalloc-8 cache

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 59bc055211b8d266ab6089158058bf8268e02006 · fixed in 8b994ac5778a725982fd6a8a3afcaa068d4a93e3; From 59bc055211b8d266ab6089158058bf8268e02006 · fixed in ad3249cdf9d4ba34bb8b1ff3956a4020fdfb5b0a; From 59bc055211b8d266ab6089158058bf8268e02006 · fixed in 85904076cece72ee3194646ad7ac8e6659d999aa; From 59bc055211b8d266ab6089158058bf8268e02006 · fixed in f03425dcbe04aec3c27b9917e97d7d23a2908dda; From 59bc055211b8d266ab6089158058bf8268e02006 · fixed in cd616aa0449a772a6956abf03358f0ff31720580; From 59bc055211b8d266ab6089158058bf8268e02006 · fixed in 9c6eace8d07e90f038c89eb3b756d65a7e259d48; From 59bc055211b8d266ab6089158058bf8268e02006 · fixed in 68d4d3e78150c7ed7d1195af63ad1e6ace30c661

  • Linux Linux

    2.6.33

  • KernelLinux

    From 2.6.33 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6

References 7

git.kernel.org