| 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-2024-58069: rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read |
| |
| The nvmem interface supports variable buffer sizes, while the regmap |
| interface operates with fixed-size storage. If an nvmem client uses a |
| buffer size less than 4 bytes, regmap_read will write out of bounds |
| as it expects the buffer to point at an unsigned int. |
| |
| Fix this by using an intermediary unsigned int to hold the value. |
| |
| The Linux kernel CVE team has assigned CVE-2024-58069 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.2 with commit fadfd092ee9138825d8c2a4f95719d2e2e3202b9 and fixed in 5.4.291 with commit 21cd59fcb9952eb7505da2bdfc1eb9c619df3ff4 |
| Issue introduced in 5.2 with commit fadfd092ee9138825d8c2a4f95719d2e2e3202b9 and fixed in 5.10.235 with commit 6f2a8ca9a0a38589f52a7f0fb9425b9ba987ae7c |
| Issue introduced in 5.2 with commit fadfd092ee9138825d8c2a4f95719d2e2e3202b9 and fixed in 5.15.179 with commit e5536677da803ed54a29a446515c28dce7d3d574 |
| Issue introduced in 5.2 with commit fadfd092ee9138825d8c2a4f95719d2e2e3202b9 and fixed in 6.1.129 with commit c72b7a474d3f445bf0c5bcf8ffed332c78eb28a1 |
| Issue introduced in 5.2 with commit fadfd092ee9138825d8c2a4f95719d2e2e3202b9 and fixed in 6.6.76 with commit 9adefa7b9559d0f21034a5d5ec1b55840c9348b9 |
| Issue introduced in 5.2 with commit fadfd092ee9138825d8c2a4f95719d2e2e3202b9 and fixed in 6.12.13 with commit e5e06455760f2995b16a176033909347929d1128 |
| Issue introduced in 5.2 with commit fadfd092ee9138825d8c2a4f95719d2e2e3202b9 and fixed in 6.13.2 with commit 517aedb365f2c94e2d7e0b908ac7127df76203a1 |
| Issue introduced in 5.2 with commit fadfd092ee9138825d8c2a4f95719d2e2e3202b9 and fixed in 6.14 with commit 3ab8c5ed4f84fa20cd16794fe8dc31f633fbc70c |
| |
| 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-2024-58069 |
| 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/rtc/rtc-pcf85063.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/21cd59fcb9952eb7505da2bdfc1eb9c619df3ff4 |
| https://git.kernel.org/stable/c/6f2a8ca9a0a38589f52a7f0fb9425b9ba987ae7c |
| https://git.kernel.org/stable/c/e5536677da803ed54a29a446515c28dce7d3d574 |
| https://git.kernel.org/stable/c/c72b7a474d3f445bf0c5bcf8ffed332c78eb28a1 |
| https://git.kernel.org/stable/c/9adefa7b9559d0f21034a5d5ec1b55840c9348b9 |
| https://git.kernel.org/stable/c/e5e06455760f2995b16a176033909347929d1128 |
| https://git.kernel.org/stable/c/517aedb365f2c94e2d7e0b908ac7127df76203a1 |
| https://git.kernel.org/stable/c/3ab8c5ed4f84fa20cd16794fe8dc31f633fbc70c |
