CVE-2022-50029

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-06-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.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:

clk: qcom: ipq8074: dont disable gcc_sleep_clk_src

Once the usb sleep clocks are disabled, clock framework is trying to disable the sleep clock source also.

However, it seems that it cannot be disabled and trying to do so produces: [ 245.436390] ------------[ cut here ]------------ [ 245.441233] gcc_sleep_clk_src status stuck at 'on' [ 245.441254] WARNING: CPU: 2 PID: 223 at clk_branch_wait+0x130/0x140 [ 245.450435] Modules linked in: xhci_plat_hcd xhci_hcd dwc3 dwc3_qcom leds_gpio [ 245.456601] CPU: 2 PID: 223 Comm: sh Not tainted 5.18.0-rc4 #215 [ 245.463889] Hardware name: Xiaomi AX9000 (DT) [ 245.470050] pstate: 204000c5 (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 245.474307] pc : clk_branch_wait+0x130/0x140 [ 245.481073] lr : clk_branch_wait+0x130/0x140 [ 245.485588] sp : ffffffc009f2bad0 [ 245.489838] x29: ffffffc009f2bad0 x28: ffffff8003e6c800 x27: 0000000000000000 [ 245.493057] x26: 0000000000000000 x25: 0000000000000000 x24: ffffff800226ef20 [ 245.500175] x23: ffffffc0089ff550 x22: 0000000000000000 x21: ffffffc008476ad0 [ 245.507294] x20: 0000000000000000 x19: ffffffc00965ac70 x18: fffffffffffc51a7 [ 245.514413] x17: 68702e3030303837 x16: 3a6d726f6674616c x15: ffffffc089f2b777 [ 245.521531] x14: ffffffc0095c9d18 x13: 0000000000000129 x12: 0000000000000129 [ 245.528649] x11: 00000000ffffffea x10: ffffffc009621d18 x9 : 0000000000000001 [ 245.535767] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : 0000000000000001 [ 245.542885] x5 : ffffff803fdca6d8 x4 : 0000000000000000 x3 : 0000000000000027 [ 245.550002] x2 : 0000000000000027 x1 : 0000000000000023 x0 : 0000000000000026 [ 245.557122] Call trace: [ 245.564229] clk_branch_wait+0x130/0x140 [ 245.566490] clk_branch2_disable+0x2c/0x40 [ 245.570656] clk_core_disable+0x60/0xb0 [ 245.574561] clk_core_disable+0x68/0xb0 [ 245.578293] clk_disable+0x30/0x50 [ 245.582113] dwc3_qcom_remove+0x60/0xc0 [dwc3_qcom] [ 245.585588] platform_remove+0x28/0x60 [ 245.590361] device_remove+0x4c/0x80 [ 245.594179] device_release_driver_internal+0x1dc/0x230 [ 245.597914] device_driver_detach+0x18/0x30 [ 245.602861] unbind_store+0xec/0x110 [ 245.607027] drv_attr_store+0x24/0x40 [ 245.610847] sysfs_kf_write+0x44/0x60 [ 245.614405] kernfs_fop_write_iter+0x128/0x1c0 [ 245.618052] new_sync_write+0xc0/0x130 [ 245.622391] vfs_write+0x1d4/0x2a0 [ 245.626123] ksys_write+0x58/0xe0 [ 245.629508] __arm64_sys_write+0x1c/0x30 [ 245.632895] invoke_syscall.constprop.0+0x5c/0x110 [ 245.636890] do_el0_svc+0xa0/0x150 [ 245.641488] el0_svc+0x18/0x60 [ 245.644872] el0t_64_sync_handler+0xa4/0x130 [ 245.647914] el0t_64_sync+0x174/0x178 [ 245.652340] ---[ end trace 0000000000000000 ]---

So, add CLK_IS_CRITICAL flag to the clock so that the kernel won't try to disable the sleep clock.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 18, 2025

Last Modified

November 13, 2025

References (7)

Vendor Advisories for CVE-2022-50029(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 4.14.291 (fixes >=4.13.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 ... 5.10.92-2 (18 versions)
  • every version up to 5.10.140-1: fixed in 5.10.140-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.2-1: fixed in 6.0.2-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 22× 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 157 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2022-50029?
CVE-2022-50029 is a medium vulnerability published on June 18, 2025. In the Linux kernel, the following vulnerability has been resolved: clk: qcom: ipq8074: dont disable gccsleepclk_src Once the usb sleep clocks are disabled, clock framework is trying to disable the sleep clock source also. However, it seems that it cannot be disabled and trying to do so produces: […
When was CVE-2022-50029 disclosed?
CVE-2022-50029 was first published on June 18, 2025, with the most recent update on November 13, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50029 actively exploited?
CVE-2022-50029 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-50029?
CVE-2022-50029 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-50029?
A fix for CVE-2022-50029 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-50029 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-50029

Explore →

Is Your Infrastructure Affected by CVE-2022-50029?

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

Book a Demo →Browse All CVEs