CVE-2022-50398

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-09-18. 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/dp: add atomic_check to bridge ops

DRM commit_tails() will disable downstream crtc/encoder/bridge if both disable crtc is required and crtc->active is set before pushing a new frame downstream.

There is a rare case that user space display manager issue an extra screen update immediately followed by close DRM device while down stream display interface is disabled. This extra screen update will timeout due to the downstream interface is disabled but will cause crtc->active be set. Hence the followed commit_tails() called by drm_release() will pass the disable downstream crtc/encoder/bridge conditions checking even downstream interface is disabled. This cause the crash to happen at dp_bridge_disable() due to it trying to access the main link register to push the idle pattern out while main link clocks is disabled.

This patch adds atomic_check to prevent the extra frame will not be pushed down if display interface is down so that crtc->active will not be set neither. This will fail the conditions checking of disabling down stream crtc/encoder/bridge which prevent drm_release() from calling dp_bridge_disable() so that crash at dp_bridge_disable() prevented.

There is no protection in the DRM framework to check if the display pipeline has been already disabled before trying again. The only check is the crtc_state->active but this is controlled by usermode using UAPI. Hence if the usermode sets this and then crashes, the driver needs to protect against double disable.

SError Interrupt on CPU7, code 0x00000000be000411 -- SError CPU: 7 PID: 3878 Comm: Xorg Not tainted 5.19.0-stb-cbq #19 Hardware name: Google Lazor (rev3 - 8) (DT) pstate: a04000c9 (NzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __cmpxchg_case_acq_32+0x14/0x2c lr : do_raw_spin_lock+0xa4/0xdc sp : ffffffc01092b6a0 x29: ffffffc01092b6a0 x28: 0000000000000028 x27: 0000000000000038 x26: 0000000000000004 x25: ffffffd2973dce48 x24: 0000000000000000 x23: 00000000ffffffff x22: 00000000ffffffff x21: ffffffd2978d0008 x20: ffffffd2978d0008 x19: ffffff80ff759fc0 x18: 0000000000000000 x17: 004800a501260460 x16: 0441043b04600438 x15: 04380000089807d0 x14: 07b0089807800780 x13: 0000000000000000 x12: 0000000000000000 x11: 0000000000000438 x10: 00000000000007d0 x9 : ffffffd2973e09e4 x8 : ffffff8092d53300 x7 : ffffff808902e8b8 x6 : 0000000000000001 x5 : ffffff808902e880 x4 : 0000000000000000 x3 : ffffff80ff759fc0 x2 : 0000000000000001 x1 : 0000000000000000 x0 : ffffff80ff759fc0 Kernel panic - not syncing: Asynchronous SError Interrupt CPU: 7 PID: 3878 Comm: Xorg Not tainted 5.19.0-stb-cbq #19 Hardware name: Google Lazor (rev3 - 8) (DT) Call trace: dump_backtrace.part.0+0xbc/0xe4 show_stack+0x24/0x70 dump_stack_lvl+0x68/0x84 dump_stack+0x18/0x34 panic+0x14c/0x32c nmi_panic+0x58/0x7c arm64_serror_panic+0x78/0x84 do_serror+0x40/0x64 el1h_64_error_handler+0x30/0x48 el1h_64_error+0x68/0x6c __cmpxchg_case_acq_32+0x14/0x2c _raw_spin_lock_irqsave+0x38/0x4c lock_timer_base+0x40/0x78 __mod_timer+0xf4/0x25c schedule_timeout+0xd4/0xfc __wait_for_common+0xac/0x140 wait_for_completion_timeout+0x2c/0x54 dp_ctrl_push_idle+0x40/0x88 dp_bridge_disable+0x24/0x30 drm_atomic_bridge_chain_disable+0x90/0xbc drm_atomic_helper_commit_modeset_disables+0x198/0x444 msm_atomic_commit_tail+0x1d0/0x374 commit_tail+0x80/0x108 drm_atomic_helper_commit+0x118/0x11c drm_atomic_commit+0xb4/0xe0 drm_client_modeset_commit_atomic+0x184/0x224 drm_client_modeset_commit_locked+0x58/0x160 drm_client_modeset_commit+0x3c/0x64 __drm_fb_helper_restore_fbdev_mode_unlocked+0x98/0xac drm_fb_helper_set_par+0x74/0x80 drm_fb_helper_hotplug_event+0xdc/0xe0 __drm_fb_helper_restore_fbdev_mode_unlocked+0x7c/0xac drm_fb_helper_restore_fbdev_mode_unlocked+0x20/0x2c drm_fb_helper_lastclose+0x20/0x2c drm_lastclose+0x44/0x6c drm_release+0x88/0xd4 __fput+0x104/0x220 ____fput+0x1c/0x28 task_work_run+0x8c/0x100 d ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

September 18, 2025

Last Modified

January 14, 2026

References (2)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.0.7—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 / 43× 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 107 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2022-50398?
CVE-2022-50398 is a medium vulnerability published on September 18, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: add atomic_check to bridge ops DRM commit_tails() will disable downstream crtc/encoder/bridge if both disable crtc is required and crtc->active is set before pushing a new frame downstream. There is a rare case that…
When was CVE-2022-50398 disclosed?
CVE-2022-50398 was first published in the National Vulnerability Database on September 18, 2025, with the most recent update on January 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50398 actively exploited?
CVE-2022-50398 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2022-50398?
CVE-2022-50398 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50398?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50398, 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-50398

Explore →

Is Your Infrastructure Affected by CVE-2022-50398?

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

Start Free Scan →Browse All CVEs