[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091550-CVE-2022-50252-5c96@gregkh>
Date: Mon, 15 Sep 2025 16:02:00 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50252: igb: Do not free q_vector unless new one was allocated
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
igb: Do not free q_vector unless new one was allocated
Avoid potential use-after-free condition under memory pressure. If the
kzalloc() fails, q_vector will be freed but left in the original
adapter->q_vector[v_idx] array position.
The Linux kernel CVE team has assigned CVE-2022-50252 to this issue.
Affected and fixed versions
===========================
Fixed in 4.9.337 with commit 64ca1969599857143e91aeec4440640656100803
Fixed in 4.14.303 with commit 0200f0fbb11e359cc35af72ab10b2ec224e6f633
Fixed in 4.19.270 with commit 68e8adbcaf7a8743e473343b38b9dad66e2ac6f3
Fixed in 5.4.229 with commit f96bd8adc8adde25390965a8c1ee81b73cb62075
Fixed in 5.10.163 with commit 3cb18dea11196fb4a06f78294cec5e61985e1aff
Fixed in 5.15.86 with commit 314f7092b27749bdde44c14095b5533afa2a3bc8
Fixed in 6.0.16 with commit 6e399577bd397a517df4b938601108c63769ce0a
Fixed in 6.1.2 with commit 56483aecf6b22eb7dff6315b3a174688c6ad494c
Fixed in 6.2 with commit 0668716506ca66f90d395f36ccdaebc3e0e84801
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-2022-50252
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/64ca1969599857143e91aeec4440640656100803
https://git.kernel.org/stable/c/0200f0fbb11e359cc35af72ab10b2ec224e6f633
https://git.kernel.org/stable/c/68e8adbcaf7a8743e473343b38b9dad66e2ac6f3
https://git.kernel.org/stable/c/f96bd8adc8adde25390965a8c1ee81b73cb62075
https://git.kernel.org/stable/c/3cb18dea11196fb4a06f78294cec5e61985e1aff
https://git.kernel.org/stable/c/314f7092b27749bdde44c14095b5533afa2a3bc8
https://git.kernel.org/stable/c/6e399577bd397a517df4b938601108c63769ce0a
https://git.kernel.org/stable/c/56483aecf6b22eb7dff6315b3a174688c6ad494c
https://git.kernel.org/stable/c/0668716506ca66f90d395f36ccdaebc3e0e84801
Powered by blists - more mailing lists