| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-23148: soc: samsung: exynos-chipid: Add NULL pointer check in exynos_chipid_probe() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| soc: samsung: exynos-chipid: Add NULL pointer check in exynos_chipid_probe() |
| |
| soc_dev_attr->revision could be NULL, thus, |
| a pointer check is added to prevent potential NULL pointer dereference. |
| This is similar to the fix in commit 3027e7b15b02 |
| ("ice: Fix some null pointer dereference issues in ice_ptp.c"). |
| |
| This issue is found by our static analysis tool. |
| |
| The Linux kernel CVE team has assigned CVE-2025-23148 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.4 with commit 3253b7b7cd44c4dd029a4ce280ef9f409a256e5f and fixed in 5.10.237 with commit 8ce469d23205249bb17c1135ccadea879576adfc |
| Issue introduced in 5.4 with commit 3253b7b7cd44c4dd029a4ce280ef9f409a256e5f and fixed in 5.15.181 with commit 8ee067cf0cf82429e9b204283c7d0d8d6891d10e |
| Issue introduced in 5.4 with commit 3253b7b7cd44c4dd029a4ce280ef9f409a256e5f and fixed in 6.1.135 with commit 475b9b45dc32eba58ab794b5d47ac689fc018398 |
| Issue introduced in 5.4 with commit 3253b7b7cd44c4dd029a4ce280ef9f409a256e5f and fixed in 6.6.88 with commit 5f80fd2ff8bfd13e41554741740e0ca8e6445ded |
| Issue introduced in 5.4 with commit 3253b7b7cd44c4dd029a4ce280ef9f409a256e5f and fixed in 6.12.24 with commit 44a2572a0fdcf3e7565763690d579b998a8f0562 |
| Issue introduced in 5.4 with commit 3253b7b7cd44c4dd029a4ce280ef9f409a256e5f and fixed in 6.13.12 with commit 4f51d169fd0d4821bce775618db024062b09a3f7 |
| Issue introduced in 5.4 with commit 3253b7b7cd44c4dd029a4ce280ef9f409a256e5f and fixed in 6.14.3 with commit 4129760e462f45f14e61b10408ace61aa7c2ed30 |
| Issue introduced in 5.4 with commit 3253b7b7cd44c4dd029a4ce280ef9f409a256e5f and fixed in 6.15 with commit c8222ef6cf29dd7cad21643228f96535cc02b327 |
| |
| 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-2025-23148 |
| 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/soc/samsung/exynos-chipid.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/8ce469d23205249bb17c1135ccadea879576adfc |
| https://git.kernel.org/stable/c/8ee067cf0cf82429e9b204283c7d0d8d6891d10e |
| https://git.kernel.org/stable/c/475b9b45dc32eba58ab794b5d47ac689fc018398 |
| https://git.kernel.org/stable/c/5f80fd2ff8bfd13e41554741740e0ca8e6445ded |
| https://git.kernel.org/stable/c/44a2572a0fdcf3e7565763690d579b998a8f0562 |
| https://git.kernel.org/stable/c/4f51d169fd0d4821bce775618db024062b09a3f7 |
| https://git.kernel.org/stable/c/4129760e462f45f14e61b10408ace61aa7c2ed30 |
| https://git.kernel.org/stable/c/c8222ef6cf29dd7cad21643228f96535cc02b327 |
