| 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-22084: w1: fix NULL pointer dereference in probe |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| w1: fix NULL pointer dereference in probe |
| |
| The w1_uart_probe() function calls w1_uart_serdev_open() (which includes |
| devm_serdev_device_open()) before setting the client ops via |
| serdev_device_set_client_ops(). This ordering can trigger a NULL pointer |
| dereference in the serdev controller's receive_buf handler, as it assumes |
| serdev->ops is valid when SERPORT_ACTIVE is set. |
| |
| This is similar to the issue fixed in commit 5e700b384ec1 |
| ("platform/chrome: cros_ec_uart: properly fix race condition") where |
| devm_serdev_device_open() was called before fully initializing the |
| device. |
| |
| Fix the race by ensuring client ops are set before enabling the port via |
| w1_uart_serdev_open(). |
| |
| The Linux kernel CVE team has assigned CVE-2025-22084 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.9 with commit a3c08804364e80328a9ffdac59bb26676b938195 and fixed in 6.12.23 with commit 4f750b84628080ff0d67bf1af67a4967b740acf2 |
| Issue introduced in 6.9 with commit a3c08804364e80328a9ffdac59bb26676b938195 and fixed in 6.13.11 with commit 64ab50577c59bb7049bec6b5c42d1c38e4029f29 |
| Issue introduced in 6.9 with commit a3c08804364e80328a9ffdac59bb26676b938195 and fixed in 6.14.2 with commit cc6b0ec7cccbf66ef3621e9e93296b7bd1f52298 |
| Issue introduced in 6.9 with commit a3c08804364e80328a9ffdac59bb26676b938195 and fixed in 6.15 with commit 0dd6770a72f138dabea9eae87f3da6ffa68f0d06 |
| |
| 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-22084 |
| 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/w1/masters/w1-uart.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/4f750b84628080ff0d67bf1af67a4967b740acf2 |
| https://git.kernel.org/stable/c/64ab50577c59bb7049bec6b5c42d1c38e4029f29 |
| https://git.kernel.org/stable/c/cc6b0ec7cccbf66ef3621e9e93296b7bd1f52298 |
| https://git.kernel.org/stable/c/0dd6770a72f138dabea9eae87f3da6ffa68f0d06 |
