---
id: CVE-2022-50498
title: 'eth: alx: take rtnl_lock on resume'
summary: |-
  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_re…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 4a5fe57e775188be96359a1934501be45fe5f705 <
    6f1991a940b90753b34570f093a21dba366e8cc0
  - >-
    Linux >= 4a5fe57e775188be96359a1934501be45fe5f705 <
    a845a0c4bdece2c0073ecea2fca7c4d5f0550f78
  - >-
    Linux >= 4a5fe57e775188be96359a1934501be45fe5f705 <
    c0323c0fd07804d5874699e93f935cda0d989c67
  - >-
    Linux >= 4a5fe57e775188be96359a1934501be45fe5f705 <
    6ad1c94e1e7e374d88f0cfd77936dddb8339aaba
  - Linux 5.14
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T20:12:25.041998Z'
published: '2025-10-04'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T20:20:49.407Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2022-50498'
references:
  - url: 'https://git.kernel.org/stable/c/6f1991a940b90753b34570f093a21dba366e8cc0'
  - url: 'https://git.kernel.org/stable/c/a845a0c4bdece2c0073ecea2fca7c4d5f0550f78'
  - url: 'https://git.kernel.org/stable/c/c0323c0fd07804d5874699e93f935cda0d989c67'
  - url: 'https://git.kernel.org/stable/c/6ad1c94e1e7e374d88f0cfd77936dddb8339aaba'
tags:
  - cve.org
epss: 0.00159
epssPercentile: 0.05086
ingestedAt: '2026-11-05T22:38:31.742Z'
---

## Overview

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.

## Affected

- `Linux >= 4a5fe57e775188be96359a1934501be45fe5f705 < 6f1991a940b90753b34570f093a21dba366e8cc0`
- `Linux >= 4a5fe57e775188be96359a1934501be45fe5f705 < a845a0c4bdece2c0073ecea2fca7c4d5f0550f78`
- `Linux >= 4a5fe57e775188be96359a1934501be45fe5f705 < c0323c0fd07804d5874699e93f935cda0d989c67`
- `Linux >= 4a5fe57e775188be96359a1934501be45fe5f705 < 6ad1c94e1e7e374d88f0cfd77936dddb8339aaba`
- `Linux 5.14`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.