[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025092300-CVE-2025-39875-6d27@gregkh>
Date: Tue, 23 Sep 2025 08:01:06 +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-39875: igb: Fix NULL pointer dereference in ethtool loopback test
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
igb: Fix NULL pointer dereference in ethtool loopback test
The igb driver currently causes a NULL pointer dereference when executing
the ethtool loopback test. This occurs because there is no associated
q_vector for the test ring when it is set up, as interrupts are typically
not added to the test rings.
Since commit 5ef44b3cb43b removed the napi_id assignment in
__xdp_rxq_info_reg(), there is no longer a need to pass a napi_id to it.
Therefore, simply use 0 as the last parameter.
The Linux kernel CVE team has assigned CVE-2025-39875 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit 2c6196013f84651772388a86dfd4bb033d0c0d45 and fixed in 6.16.8 with commit 473be7d39efd3be383e9c0c8e44b53508b4ffeb5
Issue introduced in 6.14 with commit 2c6196013f84651772388a86dfd4bb033d0c0d45 and fixed in 6.17-rc6 with commit 75871a525a596ff4d16c4aebc0018f8d0923c9b1
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-39875
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/intel/igb/igb_main.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/473be7d39efd3be383e9c0c8e44b53508b4ffeb5
https://git.kernel.org/stable/c/75871a525a596ff4d16c4aebc0018f8d0923c9b1
Powered by blists - more mailing lists