| 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-2022-49222: drm/bridge: anx7625: Fix overflow issue on reading EDID |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| drm/bridge: anx7625: Fix overflow issue on reading EDID |
| |
| The length of EDID block can be longer than 256 bytes, so we should use |
| `int` instead of `u8` for the `edid_pos` variable. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49222 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.11 with commit 8bdfc5dae4e3ba4d99dfb430ef43249e5f1b7730 and fixed in 5.15.33 with commit 64c06df2428bb7bb3d8cf5691416001af42d94dd |
| Issue introduced in 5.11 with commit 8bdfc5dae4e3ba4d99dfb430ef43249e5f1b7730 and fixed in 5.16.19 with commit f0d5d938d51af4eb08d9d8684fd9903425a0a87d |
| Issue introduced in 5.11 with commit 8bdfc5dae4e3ba4d99dfb430ef43249e5f1b7730 and fixed in 5.17.2 with commit db1c47d299298a7c52ccb201905d6be979fd7507 |
| Issue introduced in 5.11 with commit 8bdfc5dae4e3ba4d99dfb430ef43249e5f1b7730 and fixed in 5.18 with commit d5c6f647aec9ed524aedd04a3aec5ebc21d39007 |
| |
| 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-2022-49222 |
| 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: |
| drivers/gpu/drm/bridge/analogix/anx7625.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/64c06df2428bb7bb3d8cf5691416001af42d94dd |
| https://git.kernel.org/stable/c/f0d5d938d51af4eb08d9d8684fd9903425a0a87d |
| https://git.kernel.org/stable/c/db1c47d299298a7c52ccb201905d6be979fd7507 |
| https://git.kernel.org/stable/c/d5c6f647aec9ed524aedd04a3aec5ebc21d39007 |
