CVE-2022-50828

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: 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:

clk: zynqmp: Fix stack-out-of-bounds in strncpy`

"BUG: KASAN: stack-out-of-bounds in strncpy+0x30/0x68"

Linux-ATF interface is using 16 bytes of SMC payload. In case clock name is longer than 15 bytes, string terminated NULL character will not be received by Linux. Add explicit NULL character at last byte to fix issues when clock name is longer.

This fixes below bug reported by KASAN:

================================================================== BUG: KASAN: stack-out-of-bounds in strncpy+0x30/0x68 Read of size 1 at addr ffff0008c89a7410 by task swapper/0/1

CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.4.0-00396-g81ef9e7-dirty #3 Hardware name: Xilinx Versal vck190 Eval board revA (QSPI) (DT) Call trace: dump_backtrace+0x0/0x1e8 show_stack+0x14/0x20 dump_stack+0xd4/0x108 print_address_description.isra.0+0xbc/0x37c __kasan_report+0x144/0x198 kasan_report+0xc/0x18 __asan_load1+0x5c/0x68 strncpy+0x30/0x68 zynqmp_clock_probe+0x238/0x7b8 platform_drv_probe+0x6c/0xc8 really_probe+0x14c/0x418 driver_probe_device+0x74/0x130 __device_attach_driver+0xc4/0xe8 bus_for_each_drv+0xec/0x150 __device_attach+0x160/0x1d8 device_initial_probe+0x10/0x18 bus_probe_device+0xe0/0xf0 device_add+0x528/0x950 of_device_add+0x5c/0x80 of_platform_device_create_pdata+0x120/0x168 of_platform_bus_create+0x244/0x4e0 of_platform_populate+0x50/0xe8 zynqmp_firmware_probe+0x370/0x3a8 platform_drv_probe+0x6c/0xc8 really_probe+0x14c/0x418 driver_probe_device+0x74/0x130 device_driver_attach+0x94/0xa0 __driver_attach+0x70/0x108 bus_for_each_dev+0xe4/0x158 driver_attach+0x30/0x40 bus_add_driver+0x21c/0x2b8 driver_register+0xbc/0x1d0 __platform_driver_register+0x7c/0x88 zynqmp_firmware_driver_init+0x1c/0x24 do_one_initcall+0xa4/0x234 kernel_init_freeable+0x1b0/0x24c kernel_init+0x10/0x110 ret_from_fork+0x10/0x18

The buggy address belongs to the page: page:ffff0008f9be1c88 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 raw: 0008d00000000000 ffff0008f9be1c90 ffff0008f9be1c90 0000000000000000 raw: 0000000000000000 0000000000000000 00000000ffffffff page dumped because: kasan: bad access detected

addr ffff0008c89a7410 is located in stack of task swapper/0/1 at offset 112 in frame: zynqmp_clock_probe+0x0/0x7b8

this frame has 3 objects: [32, 44) 'response' [64, 80) 'ret_payload' [96, 112) 'name'

Memory state around the buggy address: ffff0008c89a7300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff0008c89a7380: 00 00 00 00 f1 f1 f1 f1 00 04 f2 f2 00 00 f2 f2 >ffff0008c89a7400: 00 00 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 ^ ffff0008c89a7480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff0008c89a7500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

December 30, 2025

Last Modified

April 15, 2026

References (6)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.4.220—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 9× in last 7d / 44× 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 144 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-27 03:39 UTCOSV refresh
  7. 2026-07-26 14:52 UTCEPSS rescore
  8. 2026-07-26 14:52 UTCEPSS rescore
  9. 2026-07-25 14:16 UTCEPSS rescore
  10. 2026-07-24 14:15 UTCEPSS rescore
  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 21:47 UTCOSV refresh
  14. 2026-07-09 19:08 UTCEPSS rescore
  15. 2026-07-08 15:13 UTCEPSS rescore
  16. 2026-07-07 13:44 UTCEPSS rescore
  17. 2026-07-06 16:25 UTCEPSS rescore
  18. 2026-07-05 02:28 UTCEPSS rescore
  19. 2026-07-04 06:29 UTCEPSS rescore
  20. 2026-07-01 15:04 UTCEPSS rescore
  21. 2026-06-30 23:21 UTCEPSS rescore
  22. 2026-06-30 23:20 UTCEPSS rescore
  23. 2026-06-29 14:04 UTCEPSS rescore
  24. 2026-06-28 14:06 UTCEPSS rescore
  25. 2026-06-28 04:54 UTCEPSS rescore
  26. 2026-06-28 04:54 UTCEPSS rescore
  27. 2026-06-27 03:07 UTCEPSS rescore
  28. 2026-06-27 03:07 UTCEPSS rescore
  29. 2026-06-25 13:48 UTCEPSS rescore
  30. 2026-06-25 13:48 UTCEPSS rescore
  31. 2026-06-24 14:03 UTCEPSS rescore
  32. 2026-06-24 14:03 UTCEPSS rescore
  33. 2026-06-23 21:31 UTCEPSS rescore
  34. 2026-06-23 21:31 UTCEPSS rescore
  35. 2026-06-22 14:24 UTCEPSS rescore
  36. 2026-06-21 14:55 UTCEPSS rescore
  37. 2026-06-21 14:55 UTCEPSS rescore
  38. 2026-06-21 08:01 UTCOSV refresh
  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-17 17:51 UTCEPSS rescore
  46. 2026-06-17 17:51 UTCEPSS rescore
  47. 2026-06-16 17:51 UTCEPSS rescore
  48. 2026-06-16 17:51 UTCEPSS rescore
  49. 2026-06-15 17:47 UTCEPSS rescore
  50. 2026-06-14 23:16 UTCEPSS rescore
  51. 2026-06-13 22:59 UTCEPSS rescore
  52. 2026-06-12 23:10 UTCEPSS rescore
  53. 2026-06-12 23:10 UTCEPSS rescore
  54. 2026-06-11 13:58 UTCEPSS rescore
  55. 2026-06-11 13:58 UTCEPSS rescore
  56. 2026-06-10 13:21 UTCEPSS rescore
  57. 2026-06-10 13:21 UTCEPSS rescore
  58. 2026-06-08 14:15 UTCEPSS rescore
  59. 2026-06-08 14:15 UTCEPSS rescore
  60. 2026-06-07 15:23 UTCEPSS rescore
  61. 2026-06-07 15:23 UTCEPSS rescore
  62. 2026-06-06 13:46 UTCEPSS rescore
  63. 2026-06-06 13:46 UTCEPSS rescore
  64. 2026-06-05 22:46 UTCEPSS rescore
  65. 2026-06-05 22:46 UTCEPSS rescore
  66. 2026-06-05 06:09 UTCEPSS rescore
  67. 2026-06-05 06:09 UTCEPSS rescore
  68. 2026-06-04 13:11 UTCEPSS rescore
  69. 2026-06-02 20:12 UTCEPSS rescore
  70. 2026-06-02 20:12 UTCEPSS rescore
  71. 2026-06-01 21:41 UTCOSV refresh
  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(4)

What is CVE-2022-50828?
CVE-2022-50828 is a publicly disclosed vulnerability published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: clk: zynqmp: Fix stack-out-of-bounds in strncpy` "BUG: KASAN: stack-out-of-bounds in strncpy+0x30/0x68" Linux-ATF interface is using 16 bytes of SMC payload. In case clock name is longer than 15 bytes, string terminated NULL…
When was CVE-2022-50828 disclosed?
CVE-2022-50828 was first published in the National Vulnerability Database on December 30, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50828 actively exploited?
CVE-2022-50828 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 88.0% of all scored CVEs.
How do I remediate CVE-2022-50828?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50828, 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-50828

Explore →

Is Your Infrastructure Affected by CVE-2022-50828?

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

Start Free Scan →Browse All CVEs