CVE-2022-50260

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-09-15. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2022-55492 (ENISA EUVD) · GHSA-wv25-jjx7-r2r4 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

drm/msm: Make .remove and .shutdown HW shutdown consistent

Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at system shutdown time to quiesce the device.

This means that some overlap exists between the two, because both have to take care of properly shutting down the hardware. But currently the logic used in these two callbacks isn't consistent in msm drivers, which could lead to kernel panic.

For example, on .remove the component is deleted and its .unbind callback leads to the hardware being shutdown but only if the DRM device has been marked as registered.

That check doesn't exist in the .shutdown logic and this can lead to the driver calling drm_atomic_helper_shutdown() for a DRM device that hasn't been properly initialized.

A situation like this can happen if drivers for expected sub-devices fail to probe, since the .bind callback will never be executed. If that is the case, drm_atomic_helper_shutdown() will attempt to take mutexes that are only initialized if drm_mode_config_init() is called during a device bind.

This bug was attempted to be fixed in commit 623f279c7781 ("drm/msm: fix shutdown hook in case GPU components failed to bind"), but unfortunately it still happens in some cases as the one mentioned above, i.e:

systemd-shutdown[1]: Powering off. kvm: exiting hardware virtualization platform wifi-firmware.0: Removing from iommu group 12 platform video-firmware.0: Removing from iommu group 10 ------------[ cut here ]------------ WARNING: CPU: 6 PID: 1 at drivers/gpu/drm/drm_modeset_lock.c:317 drm_modeset_lock_all_ctx+0x3c4/0x3d0 ... Hardware name: Google CoachZ (rev3+) (DT) pstate: a0400009 (NzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : drm_modeset_lock_all_ctx+0x3c4/0x3d0 lr : drm_modeset_lock_all_ctx+0x48/0x3d0 sp : ffff80000805bb80 x29: ffff80000805bb80 x28: ffff327c00128000 x27: 0000000000000000 x26: 0000000000000000 x25: 0000000000000001 x24: ffffc95d820ec030 x23: ffff327c00bbd090 x22: ffffc95d8215eca0 x21: ffff327c039c5800 x20: ffff327c039c5988 x19: ffff80000805bbe8 x18: 0000000000000034 x17: 000000040044ffff x16: ffffc95d80cac920 x15: 0000000000000000 x14: 0000000000000315 x13: 0000000000000315 x12: 0000000000000000 x11: 0000000000000000 x10: 0000000000000000 x9 : 0000000000000000 x8 : ffff80000805bc28 x7 : 0000000000000000 x6 : 0000000000000000 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : ffff327c00128000 x1 : 0000000000000000 x0 : ffff327c039c59b0 Call trace: drm_modeset_lock_all_ctx+0x3c4/0x3d0 drm_atomic_helper_shutdown+0x70/0x134 msm_drv_shutdown+0x30/0x40 platform_shutdown+0x28/0x40 device_shutdown+0x148/0x350 kernel_power_off+0x38/0x80 __do_sys_reboot+0x288/0x2c0 __arm64_sys_reboot+0x28/0x34 invoke_syscall+0x48/0x114 el0_svc_common.constprop.0+0x44/0xec do_el0_svc+0x2c/0xc0 el0_svc+0x2c/0x84 el0t_64_sync_handler+0x11c/0x150 el0t_64_sync+0x18c/0x190 ---[ end trace 0000000000000000 ]--- Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004 CM = 0, WnR = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=000000010eab1000 [0000000000000018] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 96000004 [#1] PREEMPT SMP ... Hardware name: Google CoachZ (rev3+) (DT) pstate: a0400009 (NzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ww_mutex_lock+0x28/0x32c lr : drm_modeset_lock_all_ctx+0x1b0/0x3d0 sp : ffff80000805bb50 x29: ffff80000805bb50 x28: ffff327c00128000 x27: 0000000000000000 x26: 00000 ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2025

Last Modified

November 25, 2025

References (3)

Vendor Advisories for CVE-2022-50260(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.19.17 (fixes >=5.9.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.3-1: fixed in 6.0.3-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 193 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 96 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-05 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-04 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-03 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-28 16:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-27 16:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-25 17:54 UTCEG score recompute
  14. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-24 17:43 UTCEG score recompute
  16. 2026-10-24 17:43 UTCVendor advisory
  17. 2026-10-24 17:43 UTCGHSA enrichmentGHSA-wv25-jjx7-r2r4 · GitHub CVSS 5.5
  18. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-22 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-18 08:19 UTCEG score recompute
  25. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 72 more
  1. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-12 18:41 UTCEG score recompute
  6. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-11 22:04 UTCEG score recompute
  8. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-08 17:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-04 23:19 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  16. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  17. 2026-10-02 05:11 UTCOSV refresh
  18. 2026-09-30 16:13 UTCEG score recompute
  19. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  20. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  21. 2026-09-26 15:55 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  22. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  23. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  24. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  26. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  27. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  28. 2026-09-13 00:36 UTCOSV refresh
  29. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  30. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  34. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  35. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  36. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  38. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  39. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  41. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  42. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  43. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  44. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  45. 2026-08-25 03:56 UTCOSV refresh
  46. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  52. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  53. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  54. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  55. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  56. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  57. 2026-08-08 21:25 UTCOSV refresh
  58. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  59. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  60. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  61. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  62. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  63. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  64. 2026-08-03 10:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  65. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  66. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  67. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  68. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  69. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  70. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  71. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  72. 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile

Frequently asked(5)

What is CVE-2022-50260?
CVE-2022-50260 is a medium-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/msm: Make .remove and .shutdown HW shutdown consistent Drivers' .remove and .shutdown callbacks are executed on different code paths. The former is called when a device is removed from the bus, while the latter is called at…
When was the CVE record for CVE-2022-50260 published?
The CVE record for CVE-2022-50260 was published on September 15, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 25, 2025; the record at its source may have been updated since.
Is CVE-2022-50260 actively exploited?
CVE-2022-50260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50260?
CVE-2022-50260 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50260?
A fix for CVE-2022-50260 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50260 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-50260

Explore →

Is Your Infrastructure Affected by CVE-2022-50260?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs