| 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-37809: usb: typec: class: Fix NULL pointer access |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| usb: typec: class: Fix NULL pointer access |
| |
| Concurrent calls to typec_partner_unlink_device can lead to a NULL pointer |
| dereference. This patch adds a mutex to protect USB device pointers and |
| prevent this issue. The same mutex protects both the device pointers and |
| the partner device registration. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37809 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.7 with commit 59de2a56d127890cc610f3896d5fc31887c54ac2 and fixed in 6.12.26 with commit de7c24febd21413ea8f49f61b36338b676c02852 |
| Issue introduced in 6.7 with commit 59de2a56d127890cc610f3896d5fc31887c54ac2 and fixed in 6.14.5 with commit 1fdde62411fe65640e69bc55ea027d5b7b2f0093 |
| Issue introduced in 6.7 with commit 59de2a56d127890cc610f3896d5fc31887c54ac2 and fixed in 6.15 with commit ec27386de23a511008c53aa2f3434ad180a3ca9a |
| |
| 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-37809 |
| 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/usb/typec/class.c |
| drivers/usb/typec/class.h |
| |
| |
| 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/de7c24febd21413ea8f49f61b36338b676c02852 |
| https://git.kernel.org/stable/c/1fdde62411fe65640e69bc55ea027d5b7b2f0093 |
| https://git.kernel.org/stable/c/ec27386de23a511008c53aa2f3434ad180a3ca9a |
