lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091508-CVE-2022-50288-3421@gregkh>
Date: Mon, 15 Sep 2025 16:21:30 +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-50288: qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

qlcnic: prevent ->dcb use-after-free on qlcnic_dcb_enable() failure

adapter->dcb would get silently freed inside qlcnic_dcb_enable() in
case qlcnic_dcb_attach() would return an error, which always happens
under OOM conditions. This would lead to use-after-free because both
of the existing callers invoke qlcnic_dcb_get_info() on the obtained
pointer, which is potentially freed at that point.

Propagate errors from qlcnic_dcb_enable(), and instead free the dcb
pointer at callsite using qlcnic_dcb_free(). This also removes the now
unused qlcnic_clear_dcb_ops() helper, which was a simple wrapper around
kfree() also causing memory leaks for partially initialized dcb.

Found by Linux Verification Center (linuxtesting.org) with the SVACE
static analysis tool.

The Linux kernel CVE team has assigned CVE-2022-50288 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 3.14 with commit 3c44bba1d270cb1620b4fe76786d0968118cb86b and fixed in 4.14.303 with commit 36999236f0b12d5de21a6f40e93b570727b9ceb2
	Issue introduced in 3.14 with commit 3c44bba1d270cb1620b4fe76786d0968118cb86b and fixed in 4.19.270 with commit d12a7510293d3370b234b0b7c5eda33e58786768
	Issue introduced in 3.14 with commit 3c44bba1d270cb1620b4fe76786d0968118cb86b and fixed in 5.4.229 with commit 8f97eeb02a553cdc78c83a0596448a370e1518c4
	Issue introduced in 3.14 with commit 3c44bba1d270cb1620b4fe76786d0968118cb86b and fixed in 5.10.163 with commit 513787ff9a331b461115e8a145a983d650a84fcb
	Issue introduced in 3.14 with commit 3c44bba1d270cb1620b4fe76786d0968118cb86b and fixed in 5.15.87 with commit 95df720e64a6409d8152827a776c43f615e3321a
	Issue introduced in 3.14 with commit 3c44bba1d270cb1620b4fe76786d0968118cb86b and fixed in 6.0.19 with commit 8df1dc04ce0e4c03b51a756749c250a9cb17d707
	Issue introduced in 3.14 with commit 3c44bba1d270cb1620b4fe76786d0968118cb86b and fixed in 6.1.5 with commit a2a694e6edbdb3efb34e1613a31fdcf6cf444a55
	Issue introduced in 3.14 with commit 3c44bba1d270cb1620b4fe76786d0968118cb86b and fixed in 6.2 with commit 13a7c8964afcd8ca43c0b6001ebb0127baa95362

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-50288
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/qlogic/qlcnic/qlcnic_83xx_init.c
	drivers/net/ethernet/qlogic/qlcnic/qlcnic_dcb.h
	drivers/net/ethernet/qlogic/qlcnic/qlcnic_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/36999236f0b12d5de21a6f40e93b570727b9ceb2
	https://git.kernel.org/stable/c/d12a7510293d3370b234b0b7c5eda33e58786768
	https://git.kernel.org/stable/c/8f97eeb02a553cdc78c83a0596448a370e1518c4
	https://git.kernel.org/stable/c/513787ff9a331b461115e8a145a983d650a84fcb
	https://git.kernel.org/stable/c/95df720e64a6409d8152827a776c43f615e3321a
	https://git.kernel.org/stable/c/8df1dc04ce0e4c03b51a756749c250a9cb17d707
	https://git.kernel.org/stable/c/a2a694e6edbdb3efb34e1613a31fdcf6cf444a55
	https://git.kernel.org/stable/c/13a7c8964afcd8ca43c0b6001ebb0127baa95362

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ