Description
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.
Product status
f400e12656ab518be107febfe2315fb1eab5a342 (git) before 60f679f643f3f36a8571ea585e4ce5d93ef952b5
f400e12656ab518be107febfe2315fb1eab5a342 (git) before 3f68a9457a6190814377577374da75f872e0a013
f400e12656ab518be107febfe2315fb1eab5a342 (git) before 0c8ab092aec3ac4294940054772d30b511b16713
f400e12656ab518be107febfe2315fb1eab5a342 (git) before 6b847d65f5b0065e02080c61fad93d57d6686383
f400e12656ab518be107febfe2315fb1eab5a342 (git) before 9e9fa5ad37c9cbad73c165c7ff1e76e650825e7c
f400e12656ab518be107febfe2315fb1eab5a342 (git) before 01ee0bcc29864b78249308e8b35042b09bbf5fe3
f400e12656ab518be107febfe2315fb1eab5a342 (git) before 3b9499e7d677dd4366239a292238489a804936b2
f400e12656ab518be107febfe2315fb1eab5a342 (git) before fdb24a820a5832ec4532273282cbd4f22c291a0d
2.6.29
Any version before 2.6.29
5.10.253 (semver)
5.15.203 (semver)
6.1.167 (semver)
6.6.130 (semver)
6.12.77 (semver)
6.18.17 (semver)
6.19.7 (semver)
7.0 (original_commit_for_fix)
References
git.kernel.org/...c/60f679f643f3f36a8571ea585e4ce5d93ef952b5
git.kernel.org/...c/3f68a9457a6190814377577374da75f872e0a013
git.kernel.org/...c/0c8ab092aec3ac4294940054772d30b511b16713
git.kernel.org/...c/6b847d65f5b0065e02080c61fad93d57d6686383
git.kernel.org/...c/9e9fa5ad37c9cbad73c165c7ff1e76e650825e7c
git.kernel.org/...c/01ee0bcc29864b78249308e8b35042b09bbf5fe3
git.kernel.org/...c/3b9499e7d677dd4366239a292238489a804936b2
git.kernel.org/...c/fdb24a820a5832ec4532273282cbd4f22c291a0d