CVE-2022-50498
Last modified
CVE-2022-50498 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.14, < 5.15.75 |
| Linux | Linux Kernel | >= 5.16, < 5.19.17 |
| Linux | Linux Kernel | >= 6.0, < 6.0.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-50498?
How severe is CVE-2022-50498?
How do I fix CVE-2022-50498?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-50492In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50493In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50494In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50495Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-50496In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50497In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-50499In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-50500In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50501In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50502Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2022-50503In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-50504In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-50498?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
