[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091657-CVE-2025-39830-5341@gregkh>
Date: Tue, 16 Sep 2025 15:08:58 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-39830: net/mlx5: HWS, Fix memory leak in hws_pool_buddy_init error path
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5: HWS, Fix memory leak in hws_pool_buddy_init error path
In the error path of hws_pool_buddy_init(), the buddy allocator cleanup
doesn't free the allocator structure itself, causing a memory leak.
Add the missing kfree() to properly release all allocated memory.
The Linux kernel CVE team has assigned CVE-2025-39830 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit c61afff94373641695cc81999e9bb10408ea84d5 and fixed in 6.16.5 with commit 86d13a6f49cb68aa91bd718b1b627e72e77285c1
Issue introduced in 6.12 with commit c61afff94373641695cc81999e9bb10408ea84d5 and fixed in 6.17-rc4 with commit 2c0a959bebdc1ada13cf9a8242f177c5400299e6
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-39830
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/ethernet/mellanox/mlx5/core/steering/hws/pool.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/86d13a6f49cb68aa91bd718b1b627e72e77285c1
https://git.kernel.org/stable/c/2c0a959bebdc1ada13cf9a8242f177c5400299e6
Powered by blists - more mailing lists