CVE-2022-49195net: dsa: fix panic on shutdown if multi-chip tree failed to probe
- 5.5MediumCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 0650bf52b31ff35dc6430fc2e37969c36baba724 – < 95df5cd5a446df6738d2d45872e08594819080e4
- affected 0650bf52b31ff35dc6430fc2e37969c36baba724 – < b6e668ff43ebd87ccc8a19e5481345c428672295
- affected 0650bf52b31ff35dc6430fc2e37969c36baba724 – < b864d5350c18bea9369d0bdd9e7eb6f6172cc283
- affected 0650bf52b31ff35dc6430fc2e37969c36baba724 – < 8fd36358ce82382519b50b05f437493e1e00c4a9
- affected 5.15
- unaffected < 5.15
- unaffected 5.15.33 – ≤ 5.15.*
- unaffected 5.16.19 – ≤ 5.16.*
- unaffected 5.17.2 – ≤ 5.17.*
- unaffected 5.18 – ≤ *
References
References4
- https://git.kernel.org/stable/c/95df5cd5a446df6738d2d45872e08594819080e4 (opens in a new tab)
- https://git.kernel.org/stable/c/b6e668ff43ebd87ccc8a19e5481345c428672295 (opens in a new tab)
- https://git.kernel.org/stable/c/b864d5350c18bea9369d0bdd9e7eb6f6172cc283 (opens in a new tab)
- https://git.kernel.org/stable/c/8fd36358ce82382519b50b05f437493e1e00c4a9 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55031 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49195)Record last updated .