linux-cve-announce - CVE-2022-50498: eth: alx: take rtnl

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: <2025100419-CVE-2022-50498-c9ab@gregkh>
Date: Sat,  4 Oct 2025 17:51:23 +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-50498: eth: alx: take rtnl_lock on resume

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

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

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

eth: alx: take rtnl_lock on resume

Zbynek reports that alx trips an rtnl assertion on resume:

 RTNL: assertion failed at net/core/dev.c (2891)
 RIP: 0010:netif_set_real_num_tx_queues+0x1ac/0x1c0
 Call Trace:
  <TASK>
  __alx_open+0x230/0x570 [alx]
  alx_resume+0x54/0x80 [alx]
  ? pci_legacy_resume+0x80/0x80
  dpm_run_callback+0x4a/0x150
  device_resume+0x8b/0x190
  async_resume+0x19/0x30
  async_run_entry_fn+0x30/0x130
  process_one_work+0x1e5/0x3b0

indeed the driver does not hold rtnl_lock during its internal close
and re-open functions during suspend/resume. Note that this is not
a huge bug as the driver implements its own locking, and does not
implement changing the number of queues, but we need to silence
the splat.

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


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

	Issue introduced in 5.14 with commit 4a5fe57e775188be96359a1934501be45fe5f705 and fixed in 5.15.75 with commit 6f1991a940b90753b34570f093a21dba366e8cc0
	Issue introduced in 5.14 with commit 4a5fe57e775188be96359a1934501be45fe5f705 and fixed in 5.19.17 with commit a845a0c4bdece2c0073ecea2fca7c4d5f0550f78
	Issue introduced in 5.14 with commit 4a5fe57e775188be96359a1934501be45fe5f705 and fixed in 6.0.3 with commit c0323c0fd07804d5874699e93f935cda0d989c67
	Issue introduced in 5.14 with commit 4a5fe57e775188be96359a1934501be45fe5f705 and fixed in 6.1 with commit 6ad1c94e1e7e374d88f0cfd77936dddb8339aaba

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-50498
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/atheros/alx/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/6f1991a940b90753b34570f093a21dba366e8cc0
	https://git.kernel.org/stable/c/a845a0c4bdece2c0073ecea2fca7c4d5f0550f78
	https://git.kernel.org/stable/c/c0323c0fd07804d5874699e93f935cda0d989c67
	https://git.kernel.org/stable/c/6ad1c94e1e7e374d88f0cfd77936dddb8339aaba