| 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-22110: netfilter: nfnetlink_queue: Initialize ctx to avoid memory allocation error |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| netfilter: nfnetlink_queue: Initialize ctx to avoid memory allocation error |
| |
| It is possible that ctx in nfqnl_build_packet_message() could be used |
| before it is properly initialize, which is only initialized |
| by nfqnl_get_sk_secctx(). |
| |
| This patch corrects this problem by initializing the lsmctx to a safe |
| value when it is declared. |
| |
| This is similar to the commit 35fcac7a7c25 |
| ("audit: Initialize lsmctx to avoid memory allocation error"). |
| |
| The Linux kernel CVE team has assigned CVE-2025-22110 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.14 with commit 2d470c778120d3cdb8d8ab250329ca85f49f12b1 and fixed in 6.14.2 with commit ddbf7e1d82a1d0c1d3425931a6cb1b83f8454759 |
| Issue introduced in 6.14 with commit 2d470c778120d3cdb8d8ab250329ca85f49f12b1 and fixed in 6.15 with commit 778b09d91baafb13408470c721d034d6515cfa5a |
| |
| 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-22110 |
| 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: |
| net/netfilter/nfnetlink_queue.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/ddbf7e1d82a1d0c1d3425931a6cb1b83f8454759 |
| https://git.kernel.org/stable/c/778b09d91baafb13408470c721d034d6515cfa5a |
