{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89947 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89947 is a high-severity memory corruption vulnerability in Linux, published on 16 Sep 2026. 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-2026-89947 and fix it if it is affected.\n\nWhat it is: CVE-2026-89947 is a high-severity memory corruption vulnerability in Linux, published on 16 Sep 2026. 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-2026-89947 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-2026-89947/ (Markdown: https://insights.sbomify.com/CVE-2026-89947/index.md)","id":"CVE-2026-89947","markdown":"https://insights.sbomify.com/CVE-2026-89947/index.md","name":"CVE-2026-89947","record":{"aliases":["AZL-101472","BELL-CVE-2026-89947","DEBIAN-CVE-2026-89947","GHSA-8jgg-jgf5-2v4q","UBUNTU-CVE-2026-89947"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel clock driver","requires_auth":"none","summary":"An out-of-bounds read in the Linux kernel Meson clock driver can cause a system crash during initialization on specific hardware.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nclk: meson: align gxbb_32k_clk_sel number of parents with actual count\n\nThe following out-of-bounds read has been observed by Christian on a\nGXBB WeTek Hub:\n==================================================================\nBUG: KASAN: global-out-of-bounds in __clk_register+0x1b70/0x2418\nRead of size 8 at addr ffffd66320cf88e0 by task swapper/0/1\n\nCPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-rc5 #1 PREEMPT\nHardware name: WeTek Hub (DT)\nCall trace:\n show_stack+0x14/0x20 (C)\n dump_stack_lvl+0x74/0x94\n print_report+0x164/0x4b0\n kasan_report+0x98/0xd8\n __asan_report_load8_noabort+0x1c/0x24\n __clk_register+0x1b70/0x2418\n devm_clk_hw_register+0x74/0x15c\n meson_clkc_init+0xd4/0x20c\n meson_clkc_syscon_probe+0x5c/0x94\n platform_probe+0xbc/0x17c\n really_probe+0x184/0x844\n __driver_probe_device+0x154/0x35c\n driver_probe_device+0x60/0x188\n __driver_attach+0x168/0x4a0\n bus_for_each_dev+0xec/0x180\n driver_attach+0x38/0x58\n bus_add_driver+0x238/0x4c0\n driver_register+0x150/0x388\n __platform_driver_register+0x54/0x7c\n gxbb_clkc_driver_init+0x18/0x20\n do_one_initcall+0xb8/0x340\n kernel_init_freeable+0x49c/0x52c\n kernel_init+0x24/0x148\n ret_from_fork+0x10/0x20\n\nThe buggy address belongs to the variable:\n gxbb_32k_clk_parents+0x60/0x400\n\nThe buggy address belongs to a vmalloc virtual mapping\nThe buggy address belongs to the physical page:\n\nMemory state around the buggy address:\n ffffd66320cf8780: 00 00 00 00 f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9\n ffffd66320cf8800: 00 04 f9 f9 f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9\n\u003effffd66320cf8880: 00 00 00 00 00 00 00 00 00 00 00 00 f9 f9 f9 f9\n                                                       ^\n ffffd66320cf8900: 00 01 f9 f9 f9 f9 f9 f9 00 06 f9 f9 f9 f9 f9 f9\n ffffd66320cf8980: 00 00 02 f9 f9 f9 f9 f9 00 00 02 f9 f9 f9 f9 f9\n==================================================================\n\nCommit 7915d7d5407c (\"clk: amlogic: gxbb: drop non existing 32k clock\nparent\") dropped a non-existing clock parent from the gxbb_32k_clk_sel\nmux but didn't adjust the hard-coded num_parents field. Fix the actual\nnumber of parents of that mux by using ARRAY_SIZE instead (avoiding\nsimilar problems in future).","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: meson: align gxbb_32k_clk_sel number of parents with actual count","id":"CVE-2026-89947","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"batman-adv: bla: fix freeing of claims on meshif deletion","id":"CVE-2026-89948"},"packages":[],"prev":{"headline":"ASoC: cs35l33: drain threaded IRQ before runtime suspend","id":"CVE-2026-89946"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An out-of-bounds read in the Linux kernel Meson clock driver can cause a system crash during initialization on specific hardware.","url":"https://insights.sbomify.com/CVE-2026-89947/"}