| 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-37757: tipc: fix memory leak in tipc_link_xmit |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| tipc: fix memory leak in tipc_link_xmit |
| |
| In case the backlog transmit queue for system-importance messages is overloaded, |
| tipc_link_xmit() returns -ENOBUFS but the skb list is not purged. This leads to |
| memory leak and failure when a skb is allocated. |
| |
| This commit fixes this issue by purging the skb list before tipc_link_xmit() |
| returns. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37757 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 5.4.293 with commit 84895f5ce3829d9fc030e5ec2d8729da4c0c9d08 |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 5.10.237 with commit d4d40e437adb376be16b3a12dd5c63f0fa768247 |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 5.15.181 with commit ed06675d3b8cd37120b447646d53f7cd3e6fcd63 |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 6.1.135 with commit 24e6280cdd7f8d01fc6b9b365fb800c2fb7ea9bb |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 6.6.88 with commit 09c2dcda2c551bba30710c33f6ac678ae7395389 |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 6.12.24 with commit 7c5957f7905b4aede9d7a559d271438f3ca9e852 |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 6.13.12 with commit d0e02d3d27a0b4dcb13f954f537ca1dd8f282dcf |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 6.14.3 with commit a40cbfbb8f95c325430f017883da669b2aa927d4 |
| Issue introduced in 4.11 with commit 365ad353c2564bba8835290061308ba825166b3a and fixed in 6.15 with commit 69ae94725f4fc9e75219d2d69022029c5b24bc9a |
| |
| 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-37757 |
| 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/tipc/link.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/84895f5ce3829d9fc030e5ec2d8729da4c0c9d08 |
| https://git.kernel.org/stable/c/d4d40e437adb376be16b3a12dd5c63f0fa768247 |
| https://git.kernel.org/stable/c/ed06675d3b8cd37120b447646d53f7cd3e6fcd63 |
| https://git.kernel.org/stable/c/24e6280cdd7f8d01fc6b9b365fb800c2fb7ea9bb |
| https://git.kernel.org/stable/c/09c2dcda2c551bba30710c33f6ac678ae7395389 |
| https://git.kernel.org/stable/c/7c5957f7905b4aede9d7a559d271438f3ca9e852 |
| https://git.kernel.org/stable/c/d0e02d3d27a0b4dcb13f954f537ca1dd8f282dcf |
| https://git.kernel.org/stable/c/a40cbfbb8f95c325430f017883da669b2aa927d4 |
| https://git.kernel.org/stable/c/69ae94725f4fc9e75219d2d69022029c5b24bc9a |
