CVE-2022-50260

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

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 / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.19.17—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.

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 105 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2022-50260?
CVE-2022-50260 is a medium vulnerability 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 CVE-2022-50260 disclosed?
CVE-2022-50260 was first published in the National Vulnerability Database on September 15, 2025, with the most recent update on November 25, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50260 actively exploited?
CVE-2022-50260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.9% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50260, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs