Squashfs: check metadata block offset is within range

Summary

In the Linux kernel, the following vulnerability has been resolved: Squashfs: check metadata block offset is within range Syzkaller reports a "general protection fault in squashfs_copy_data" This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block offset. This is subsequently passed to squashfs_copy_data (via squashfs_read_metadata) where the negative offset causes an out of bounds access. The fix is to check that the offset is within range in squashfs_read_metadata. This will trap this and other cases.

Timeline

1. Mar 25, 2026, 10:28 AM UTCCVE published
2. Oct 15, 2026, 1:14 AM UTCRecord last updated

Affected versions

• Linux Linux

  From f400e12656ab518be107febfe2315fb1eab5a342 · fixed in 60f679f643f3f36a8571ea585e4ce5d93ef952b5; From f400e12656ab518be107febfe2315fb1eab5a342 · fixed in 3f68a9457a6190814377577374da75f872e0a013; From f400e12656ab518be107febfe2315fb1eab5a342 · fixed in 0c8ab092aec3ac4294940054772d30b511b16713; From f400e12656ab518be107febfe2315fb1eab5a342 · fixed in 6b847d65f5b0065e02080c61fad93d57d6686383; From f400e12656ab518be107febfe2315fb1eab5a342 · fixed in 9e9fa5ad37c9cbad73c165c7ff1e76e650825e7c; From f400e12656ab518be107febfe2315fb1eab5a342 · fixed in 01ee0bcc29864b78249308e8b35042b09bbf5fe3; From f400e12656ab518be107febfe2315fb1eab5a342 · fixed in 3b9499e7d677dd4366239a292238489a804936b2; From f400e12656ab518be107febfe2315fb1eab5a342 · fixed in fdb24a820a5832ec4532273282cbd4f22c291a0d

• Linux Linux

  2.6.29

• KernelLinux

  From 2.6.29 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.167; From 6.2.0 · fixed in 6.6.130; From 6.7.0 · fixed in 6.12.77; From 6.13.0 · fixed in 6.18.17; From 6.19.0 · fixed in 6.19.7

References 8