| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-21798: firewire: test: Fix potential null dereference in firewire kunit test |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| firewire: test: Fix potential null dereference in firewire kunit test |
| |
| kunit_kzalloc() may return a NULL pointer, dereferencing it without |
| NULL check may lead to NULL dereference. |
| Add a NULL check for test_state. |
| |
| The Linux kernel CVE team has assigned CVE-2025-21798 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.8 with commit 1c8506d62624fbc57db75414a387f365da8422e9 and fixed in 6.12.13 with commit c6896bf4c611c3dd126f3e03685f2360a18b3d6f |
| Issue introduced in 6.8 with commit 1c8506d62624fbc57db75414a387f365da8422e9 and fixed in 6.13.2 with commit 70fcb25472d90dd3b87cbee74b9eb68670b0c7b8 |
| Issue introduced in 6.8 with commit 1c8506d62624fbc57db75414a387f365da8422e9 and fixed in 6.14 with commit 352fafe97784e81a10a7c74bd508f71a19b53c2a |
| |
| 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-21798 |
| 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/firewire/device-attribute-test.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/c6896bf4c611c3dd126f3e03685f2360a18b3d6f |
| https://git.kernel.org/stable/c/70fcb25472d90dd3b87cbee74b9eb68670b0c7b8 |
| https://git.kernel.org/stable/c/352fafe97784e81a10a7c74bd508f71a19b53c2a |
