| 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-37862: HID: pidff: Fix null pointer dereference in pidff_find_fields |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| HID: pidff: Fix null pointer dereference in pidff_find_fields |
| |
| This function triggered a null pointer dereference if used to search for |
| a report that isn't implemented on the device. This happened both for |
| optional and required reports alike. |
| |
| The same logic was applied to pidff_find_special_field and although |
| pidff_init_fields should return an error earlier if one of the required |
| reports is missing, future modifications could change this logic and |
| resurface this possible null pointer dereference again. |
| |
| LKML bug report: |
| https://lore.kernel.org/all/CAL-gK7f5=R0nrrQdPtaZZr1fd-cdAMbDMuZ_NLA8vM0SX+nGSw@mail.gmail.com |
| |
| The Linux kernel CVE team has assigned CVE-2025-37862 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.4.293 with commit 44a1b8b2027afbb37e418993fb23561bdb9efb38 |
| Fixed in 5.10.237 with commit d230becb9d38b7325c5c38d051693e4c26b1829b |
| Fixed in 5.15.181 with commit 6b4449e4f03326fbd2136e67bfcc1e6ffe61541d |
| Fixed in 6.1.135 with commit ddb147885225d768025f6818df533d30edf3e102 |
| Fixed in 6.6.88 with commit be706a48bb7896d4130edc82811233d1d62158e7 |
| Fixed in 6.12.24 with commit f8f4d77710e1c38f4a2bd26c88c4878b5b5e817a |
| Fixed in 6.13.12 with commit 3a507184f9307e19cb441b897c49e7843c94e56b |
| Fixed in 6.14.3 with commit e368698da79af821f18c099520deab1219c2044b |
| Fixed in 6.15 with commit 22a05462c3d0eee15154faf8d13c49e6295270a5 |
| |
| 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-37862 |
| 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/hid/usbhid/hid-pidff.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/44a1b8b2027afbb37e418993fb23561bdb9efb38 |
| https://git.kernel.org/stable/c/d230becb9d38b7325c5c38d051693e4c26b1829b |
| https://git.kernel.org/stable/c/6b4449e4f03326fbd2136e67bfcc1e6ffe61541d |
| https://git.kernel.org/stable/c/ddb147885225d768025f6818df533d30edf3e102 |
| https://git.kernel.org/stable/c/be706a48bb7896d4130edc82811233d1d62158e7 |
| https://git.kernel.org/stable/c/f8f4d77710e1c38f4a2bd26c88c4878b5b5e817a |
| https://git.kernel.org/stable/c/3a507184f9307e19cb441b897c49e7843c94e56b |
| https://git.kernel.org/stable/c/e368698da79af821f18c099520deab1219c2044b |
| https://git.kernel.org/stable/c/22a05462c3d0eee15154faf8d13c49e6295270a5 |
