| 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-57910: iio: light: vcnl4035: fix information leak in triggered buffer |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| iio: light: vcnl4035: fix information leak in triggered buffer |
| |
| The 'buffer' local array is used to push data to userspace from a |
| triggered buffer, but it does not set an initial value for the single |
| data element, which is an u16 aligned to 8 bytes. That leaves at least |
| 4 bytes uninitialized even after writing an integer value with |
| regmap_read(). |
| |
| Initialize the array to zero before using it to avoid pushing |
| uninitialized information to userspace. |
| |
| The Linux kernel CVE team has assigned CVE-2024-57910 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.4.132 with commit da8ef748fec2d55db0ae424ab40eee0c737564aa and fixed in 5.4.290 with commit 13e56229fc81051a42731046e200493c4a7c28ff |
| Issue introduced in 5.10.50 with commit 49739675048d372946c1ef136c466d5675eba9f0 and fixed in 5.10.234 with commit b0e9c11c762e4286732d80e66c08c2cb3157b06b |
| Issue introduced in 5.14 with commit ec90b52c07c0403a6db60d752484ec08d605ead0 and fixed in 5.15.177 with commit cb488706cdec0d6d13f2895bcdf0c32b283a7cc7 |
| Issue introduced in 5.14 with commit ec90b52c07c0403a6db60d752484ec08d605ead0 and fixed in 6.1.125 with commit 47d245be86492974db3aeb048609542167f56518 |
| Issue introduced in 5.14 with commit ec90b52c07c0403a6db60d752484ec08d605ead0 and fixed in 6.6.72 with commit a15ea87d4337479c9446b5d71616f4668337afed |
| Issue introduced in 5.14 with commit ec90b52c07c0403a6db60d752484ec08d605ead0 and fixed in 6.12.10 with commit f6fb1c59776b4263634c472a5be8204c906ffc2c |
| Issue introduced in 5.14 with commit ec90b52c07c0403a6db60d752484ec08d605ead0 and fixed in 6.13 with commit 47b43e53c0a0edf5578d5d12f5fc71c019649279 |
| Issue introduced in 5.12.17 with commit d69f0d132563a63688efb0afb4dfeaa74a217306 |
| Issue introduced in 5.13.2 with commit 4637815d7922c4bce3bacb13dd1fb5e9a7d167d8 |
| |
| 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-57910 |
| 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/iio/light/vcnl4035.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/13e56229fc81051a42731046e200493c4a7c28ff |
| https://git.kernel.org/stable/c/b0e9c11c762e4286732d80e66c08c2cb3157b06b |
| https://git.kernel.org/stable/c/cb488706cdec0d6d13f2895bcdf0c32b283a7cc7 |
| https://git.kernel.org/stable/c/47d245be86492974db3aeb048609542167f56518 |
| https://git.kernel.org/stable/c/a15ea87d4337479c9446b5d71616f4668337afed |
| https://git.kernel.org/stable/c/f6fb1c59776b4263634c472a5be8204c906ffc2c |
| https://git.kernel.org/stable/c/47b43e53c0a0edf5578d5d12f5fc71c019649279 |
