Squashfs: check metadata block offset is within range
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f400e12656ab518be107febfe2315fb1eab5a342 · < 01ee0bcc29864b78249308e8b35042b09bbf5fe3| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
A corrupted Squashfs index lookup table can produce a negative metadata block offset, causing an out-of-bounds access in the Linux kernel. The report describes a general protection fault; it does not specify how an attacker could supply the corrupted data or whether authentication or user interaction is required.
Engineers running Linux kernels with Squashfs support should check their vendor's advisory; affected versions are not specified.