[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050127-CVE-2022-49805-56c1@gregkh>
Date: Thu, 1 May 2025 16:09:55 +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-49805: net: lan966x: Fix potential null-ptr-deref in lan966x_stats_init()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: lan966x: Fix potential null-ptr-deref in lan966x_stats_init()
lan966x_stats_init() calls create_singlethread_workqueue() and not
checked the ret value, which may return NULL. And a null-ptr-deref may
happen:
lan966x_stats_init()
create_singlethread_workqueue() # failed, lan966x->stats_queue is NULL
queue_delayed_work()
queue_delayed_work_on()
__queue_delayed_work() # warning here, but continue
__queue_work() # access wq->flags, null-ptr-deref
Check the ret value and return -ENOMEM if it is NULL.
The Linux kernel CVE team has assigned CVE-2022-49805 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.17 with commit 12c2d0a5b8e2a1afc8c7738e19a0d1dd7f3d4007 and fixed in 6.0.10 with commit 4a43c1c6040e848e1344c7b16ac696b68fbc439c
Issue introduced in 5.17 with commit 12c2d0a5b8e2a1afc8c7738e19a0d1dd7f3d4007 and fixed in 6.1 with commit ba86af3733aece88dbcee0dfebf7e2dcfefb2be4
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-49805
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/microchip/lan966x/lan966x_ethtool.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/4a43c1c6040e848e1344c7b16ac696b68fbc439c
https://git.kernel.org/stable/c/ba86af3733aece88dbcee0dfebf7e2dcfefb2be4
Powered by blists - more mailing lists