| 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-39755: staging: gpib: Fix cb7210 pcmcia Oops |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| staging: gpib: Fix cb7210 pcmcia Oops |
| |
| The pcmcia_driver struct was still only using the old .name |
| initialization in the drv field. This led to a NULL pointer |
| deref Oops in strcmp called from pcmcia_register_driver. |
| |
| Initialize the pcmcia_driver struct name field. |
| |
| The Linux kernel CVE team has assigned CVE-2025-39755 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.13 with commit e9dc69956d4d9bf4a81d35995ce9229ff5e4cad5 and fixed in 6.13.11 with commit 7ec50077d7f6647cb6ba3a2a20a6c26f51259c7d |
| Issue introduced in 6.13 with commit e9dc69956d4d9bf4a81d35995ce9229ff5e4cad5 and fixed in 6.14.2 with commit c82ae06f49e70d1c14ee9c76c392345856d050c9 |
| Issue introduced in 6.13 with commit e9dc69956d4d9bf4a81d35995ce9229ff5e4cad5 and fixed in 6.15 with commit c1baf6528bcfd6a86842093ff3f8ff8caf309c12 |
| |
| 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-39755 |
| 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/staging/gpib/cb7210/cb7210.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/7ec50077d7f6647cb6ba3a2a20a6c26f51259c7d |
| https://git.kernel.org/stable/c/c82ae06f49e70d1c14ee9c76c392345856d050c9 |
| https://git.kernel.org/stable/c/c1baf6528bcfd6a86842093ff3f8ff8caf309c12 |
