CVE-2022-49195
Last modified
CVE-2022-49195 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net: dsa: fix panic on shutdown if multi-chip tree failed to probe DSA probing is atypical because a tree of devices must probe all at once, so out of N switches which call dsa_tree_setup_routing_table() during probe, for (N - 1) of them, "complete" will return false and they will exit probing early. The Nth switch will set up the whole tree on their behalf. The implication is that for (N - 1) switches, the driver binds to the device successfully, without doing anything. EPSS estimates a 0.24% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net: dsa: fix panic on shutdown if multi-chip tree failed to probe DSA probing is atypical because a tree of devices must probe all at once, so out of N switches which call dsa_tree_setup_routing_table() during probe, for (N - 1) of them, "complete" will return false and they will exit probing early. The Nth switch will set up the whole tree on their behalf. The implication is that for (N - 1) switches, the driver binds to the device successfully, without doing anything. When the driver is bound, the ->shutdown() method may run. But if the Nth switch has failed to initialize the tree, there is nothing to do for the (N - 1) driver instances, since the slave devices have not been created, etc. Moreover, dsa_switch_shutdown() expects that the calling @ds has been in fact initialized, so it jumps at dereferencing the various data structures, which is incorrect. Avoid the ensuing NULL pointer dereferences by simply checking whether the Nth switch has previously set "ds->setup = true" for the switch which is currently shutting down. The entire setup is serialized under dsa2_mutex which we already hold.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.15.1, < 5.15.33 |
| Linux | Linux Kernel | >= 5.16, < 5.16.19 |
| Linux | Linux Kernel | >= 5.17, < 5.17.2 |
| Linux | Linux Kernel | 5.15 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-49195?
How severe is CVE-2022-49195?
How do I fix CVE-2022-49195?
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-4919Use after free in Base Internals in Google Chrome prior to 1…8.8
- CVE-2022-49190In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49191In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49192In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49193In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49194In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49196In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-49197In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49198In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49199In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-4920Heap buffer overflow in Blink in Google Chrome prior to 101.…9.6
- CVE-2022-49200In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49195?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
