| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2023-52979: squashfs: harden sanity check in squashfs_read_xattr_id_table |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| squashfs: harden sanity check in squashfs_read_xattr_id_table |
| |
| While mounting a corrupted filesystem, a signed integer '*xattr_ids' can |
| become less than zero. This leads to the incorrect computation of 'len' |
| and 'indexes' values which can cause null-ptr-deref in copy_bio_to_actor() |
| or out-of-bounds accesses in the next sanity checks inside |
| squashfs_read_xattr_id_table(). |
| |
| Found by Linux Verification Center (linuxtesting.org) with Syzkaller. |
| |
| The Linux kernel CVE team has assigned CVE-2023-52979 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.14.222 with commit ff49cace7b8cf00d27665f7536a863d406963d06 and fixed in 4.14.306 with commit cf5d6612092408157db6bb500c70bf6d67c40fbc |
| Issue introduced in 4.19.176 with commit a8717b34003f4f7353b23826617ad872f85d85d8 and fixed in 4.19.273 with commit b30a74f83265c24d1d0842c6c3928cd2e775a3fb |
| Issue introduced in 5.4.98 with commit 3654a0ed0bdc6d70502bfc7c9fec9f1e243dfcad and fixed in 5.4.232 with commit db76fc535fbdfbf29fd0b93e49627537ad794c8c |
| Issue introduced in 5.10.16 with commit bddcce15cd1fb9675ddd46a76d8fe2d0a571313b and fixed in 5.10.168 with commit de2785aa3448d1ee7be3ab47fd4a873025f1b3d7 |
| Issue introduced in 5.11 with commit 506220d2ba21791314af569211ffd8870b8208fa and fixed in 5.15.93 with commit b7398efe24a965cf3937b716c0b1011c201c5d6e |
| Issue introduced in 5.11 with commit 506220d2ba21791314af569211ffd8870b8208fa and fixed in 6.1.11 with commit 29e774dcb27116c06b9c57b1f1f14a1623738989 |
| Issue introduced in 5.11 with commit 506220d2ba21791314af569211ffd8870b8208fa and fixed in 6.2 with commit 72e544b1b28325fe78a4687b980871a7e4101f76 |
| Issue introduced in 4.4.258 with commit 91d4f4d0d7bcd6abd9f9288ff40f4edc716f3d4b |
| Issue introduced in 4.9.258 with commit eca93bf20f70e0f78c8c28720951942f61a49117 |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2023-52979 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| fs/squashfs/xattr_id.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/cf5d6612092408157db6bb500c70bf6d67c40fbc |
| https://git.kernel.org/stable/c/b30a74f83265c24d1d0842c6c3928cd2e775a3fb |
| https://git.kernel.org/stable/c/db76fc535fbdfbf29fd0b93e49627537ad794c8c |
| https://git.kernel.org/stable/c/de2785aa3448d1ee7be3ab47fd4a873025f1b3d7 |
| https://git.kernel.org/stable/c/b7398efe24a965cf3937b716c0b1011c201c5d6e |
| https://git.kernel.org/stable/c/29e774dcb27116c06b9c57b1f1f14a1623738989 |
| https://git.kernel.org/stable/c/72e544b1b28325fe78a4687b980871a7e4101f76 |
