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.
Conclusion & alert: CVE-2022-49195 is rated Low Risk (29.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.07%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
| # | Date | Old EPSS score | New EPSS score | Delta (New - Old) |
|---|---|---|---|---|
| 1 | 2026-04-06 | 0.04% | 0.07% | +0.03% |
| 2 | 2026-02-19 | 0.06% | 0.04% | -0.02% |
| 3 | 2025-08-06 | — | 0.06% | — |
Full EPSS history (4 records total)
CVSS metrics for this CVE.
| Base score | Version | Severity | Vector | Exploitability | Impact | Score source |
|---|---|---|---|---|---|---|
| 5.5 | 3.1 | MEDIUM |
|
1.8 | 3.6 | [email protected] |
| vendor | priority | summary | link |
|---|---|---|---|
debian
|
unimportant | CVE-2022-49195 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. | https://security-tracker.debian.org/tracker/CVE-2022-49195 |
redhat
|
— | — | https://access.redhat.com/security/cve/CVE-2022-49195 |
suse
|
medium | CVE-2022-49195 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 270 product×package rows across 54 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 12 SP5, … (54 product lines)): Known Not Affected 270. | https://www.suse.com/security/cve/CVE-2022-49195/ |
ubuntu
|
medium | CVE-2022-49195 medium priority: Ubuntu including 130 source packages (linux, linux-allwinner-5.19, …), 1040 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 713, ignored 146, not-affected 101, released 80. | https://ubuntu.com/security/CVE-2022-49195 |
| Vendor | Product | Version | Raw CPE |
|---|---|---|---|
| linux | linux_kernel | >= 5.15.1, < 5.15.33 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 5.16, < 5.16.19 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | >= 5.17, < 5.17.2 | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
| linux | linux_kernel | 5.15 | cpe:2.3:o:linux:linux_kernel:5.15:-:*:*:*:*:*:* |
| linux | linux_kernel | 5.15 | cpe:2.3:o:linux:linux_kernel:5.15:rc3:*:*:*:*:*:* |
| linux | linux_kernel | 5.15 | cpe:2.3:o:linux:linux_kernel:5.15:rc4:*:*:*:*:*:* |
| linux | linux_kernel | 5.15 | cpe:2.3:o:linux:linux_kernel:5.15:rc5:*:*:*:*:*:* |
| linux | linux_kernel | 5.15 | cpe:2.3:o:linux:linux_kernel:5.15:rc6:*:*:*:*:*:* |
| linux | linux_kernel | 5.15 | cpe:2.3:o:linux:linux_kernel:5.15:rc7:*:*:*:*:*:* |