| From bippy-7c5fe7eed585 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-21903: mctp i3c: handle NULL header address |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| mctp i3c: handle NULL header address |
| |
| daddr can be NULL if there is no neighbour table entry present, |
| in that case the tx packet should be dropped. |
| |
| saddr will usually be set by MCTP core, but check for NULL in case a |
| packet is transmitted by a different protocol. |
| |
| The Linux kernel CVE team has assigned CVE-2025-21903 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.7 with commit c8755b29b58ec65be17bcb8c40763d2dcb1f1db5 and fixed in 6.12.19 with commit d8be54c35aee29d96d1350b1b6f153be4da37c07 |
| Issue introduced in 6.7 with commit c8755b29b58ec65be17bcb8c40763d2dcb1f1db5 and fixed in 6.13.7 with commit 740bf9c9b715cc327d34b1e2d4ee79fcd4c47a56 |
| Issue introduced in 6.7 with commit c8755b29b58ec65be17bcb8c40763d2dcb1f1db5 and fixed in 6.14 with commit cf7ee25e70c6edfac4553d6b671e8b19db1d9573 |
| |
| 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-21903 |
| 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/net/mctp/mctp-i3c.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/d8be54c35aee29d96d1350b1b6f153be4da37c07 |
| https://git.kernel.org/stable/c/740bf9c9b715cc327d34b1e2d4ee79fcd4c47a56 |
| https://git.kernel.org/stable/c/cf7ee25e70c6edfac4553d6b671e8b19db1d9573 |
