Answer in brief
CVE-2022-50498 records a Medium severity (CVSS 5.5) vulnerability in eth: alx: take rtnl_lock on resume. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4a5fe57e775188be96359a1934501be45fe5f705 <6f1991a940b90753b34570f093a21dba366e8cc0 || >=4a5fe57e775188be96359a1934501be45fe5f705 <a845a0c4bdece2c0073ecea2fca7c4d5f0550f78 || >=4a5fe57e775188be96359a1934501be45fe5f705 <c0323c0fd07804d5874699e93f935cda0d989c67 || >=4a5fe57e775188be96359a1934501be45fe5f705 <6ad1c94e1e7e374d88f0cfd77936dddb8339aaba | 6f1991a940b90753b34570f093a21dba366e8cc0, a845a0c4bdece2c0073ecea2fca7c4d5f0550f78, c0323c0fd07804d5874699e93f935cda0d989c67, 6ad1c94e1e7e374d88f0cfd77936dddb8339aaba |
| Linux/Linuxgeneric | 5.14 | Not reported |
Published upstream
Oct 4, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.