{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50828 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50828 is a memory corruption vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50828 and fix it if it is affected.\n\nWhat it is: CVE-2022-50828 is a memory corruption vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50828 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50828/ (Markdown: https://insights.sbomify.com/CVE-2022-50828/index.md)","id":"CVE-2022-50828","markdown":"https://insights.sbomify.com/CVE-2022-50828/index.md","name":"CVE-2022-50828","record":{"aliases":["DEBIAN-CVE-2022-50828","GHSA-m8pm-m36r-6prw","UBUNTU-CVE-2022-50828"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A stack-out-of-bounds read in the ZynqMP clock driver can cause a kernel crash when processing long clock names.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nclk: zynqmp: Fix stack-out-of-bounds in strncpy`\n\n\"BUG: KASAN: stack-out-of-bounds in strncpy+0x30/0x68\"\n\nLinux-ATF interface is using 16 bytes of SMC payload. In case clock name is\nlonger than 15 bytes, string terminated NULL character will not be received\nby Linux. Add explicit NULL character at last byte to fix issues when clock\nname is longer.\n\nThis fixes below bug reported by KASAN:\n\n ==================================================================\n BUG: KASAN: stack-out-of-bounds in strncpy+0x30/0x68\n Read of size 1 at addr ffff0008c89a7410 by task swapper/0/1\n\n CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.4.0-00396-g81ef9e7-dirty #3\n Hardware name: Xilinx Versal vck190 Eval board revA (QSPI) (DT)\n Call trace:\n  dump_backtrace+0x0/0x1e8\n  show_stack+0x14/0x20\n  dump_stack+0xd4/0x108\n  print_address_description.isra.0+0xbc/0x37c\n  __kasan_report+0x144/0x198\n  kasan_report+0xc/0x18\n  __asan_load1+0x5c/0x68\n  strncpy+0x30/0x68\n  zynqmp_clock_probe+0x238/0x7b8\n  platform_drv_probe+0x6c/0xc8\n  really_probe+0x14c/0x418\n  driver_probe_device+0x74/0x130\n  __device_attach_driver+0xc4/0xe8\n  bus_for_each_drv+0xec/0x150\n  __device_attach+0x160/0x1d8\n  device_initial_probe+0x10/0x18\n  bus_probe_device+0xe0/0xf0\n  device_add+0x528/0x950\n  of_device_add+0x5c/0x80\n  of_platform_device_create_pdata+0x120/0x168\n  of_platform_bus_create+0x244/0x4e0\n  of_platform_populate+0x50/0xe8\n  zynqmp_firmware_probe+0x370/0x3a8\n  platform_drv_probe+0x6c/0xc8\n  really_probe+0x14c/0x418\n  driver_probe_device+0x74/0x130\n  device_driver_attach+0x94/0xa0\n  __driver_attach+0x70/0x108\n  bus_for_each_dev+0xe4/0x158\n  driver_attach+0x30/0x40\n  bus_add_driver+0x21c/0x2b8\n  driver_register+0xbc/0x1d0\n  __platform_driver_register+0x7c/0x88\n  zynqmp_firmware_driver_init+0x1c/0x24\n  do_one_initcall+0xa4/0x234\n  kernel_init_freeable+0x1b0/0x24c\n  kernel_init+0x10/0x110\n  ret_from_fork+0x10/0x18\n\n The buggy address belongs to the page:\n page:ffff0008f9be1c88 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0\n raw: 0008d00000000000 ffff0008f9be1c90 ffff0008f9be1c90 0000000000000000\n raw: 0000000000000000 0000000000000000 00000000ffffffff\n page dumped because: kasan: bad access detected\n\n addr ffff0008c89a7410 is located in stack of task swapper/0/1 at offset 112 in frame:\n  zynqmp_clock_probe+0x0/0x7b8\n\n this frame has 3 objects:\n  [32, 44) 'response'\n  [64, 80) 'ret_payload'\n  [96, 112) 'name'\n\n Memory state around the buggy address:\n  ffff0008c89a7300: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n  ffff0008c89a7380: 00 00 00 00 f1 f1 f1 f1 00 04 f2 f2 00 00 f2 f2\n \u003effff0008c89a7400: 00 00 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00\n                          ^\n  ffff0008c89a7480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n  ffff0008c89a7500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n ==================================================================","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"clk: zynqmp: Fix stack-out-of-bounds in strncpy`","id":"CVE-2022-50828","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"wifi: ath9k: hif_usb: Fix use-after-free in ath9k_hif_usb_reg_in_cb()","id":"CVE-2022-50829"},"packages":[],"prev":{"headline":"scsi: lpfc: Fix memory leak in lpfc_create_port()","id":"CVE-2022-50827"},"products":["Linux"],"published":"2025-12-30","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A stack-out-of-bounds read in the ZynqMP clock driver can cause a kernel crash when processing long clock names.","url":"https://insights.sbomify.com/CVE-2022-50828/"}