CVE-2026-89947

CVE CVE-2026-89947EUVD EUVD-2026-80547Published 2026-09-16T10:32:33.000ZLast changed 2026-09-16T14:40:32.000ZCVSS 8.0

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: clk: meson: align gxbb_32k_clk_sel number of parents with actual count The following out-of-bounds read has been observed by Christian on a GXBB WeTek Hub: ================================================================== BUG: KASAN: global-out-of-bounds in __clk_register+0x1b70/0x2418 Read of size 8 at addr ffffd66320cf88e0 by task swapper/0/1 CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 7.0.0-rc5 #1 PREEMPT Hardware name: WeTek Hub (DT) Call trace: show_stack+0x14/0x20 (C) dump_stack_lvl+0x74/0x94 print_report+0x164/0x4b0 kasan_report+0x98/0xd8 __asan_report_load8_noabort+0x1c/0x24 __clk_register+0x1b70/0x2418 devm_clk_hw_register+0x74/0x15c meson_clkc_init+0xd4/0x20c meson_clkc_syscon_probe+0x5c/0x94 platform_probe+0xbc/0x17c really_probe+0x184/0x844 __driver_probe_device+0x154/0x35c driver_probe_device+0x60/0x188 __driver_attach+0x168/0x4a0 bus_for_each_dev+0xec/0x180 driver_attach+0x38/0x58 bus_add_driver+0x238/0x4c0 driver_register+0x150/0x388 __platform_driver_register+0x54/0x7c gxbb_clkc_driver_init+0x18/0x20 do_one_initcall+0xb8/0x340 kernel_init_freeable+0x49c/0x52c kernel_init+0x24/0x148 ret_from_fork+0x10/0x20 The buggy address belongs to the variable: gxbb_32k_clk_parents+0x60/0x400 The buggy address belongs to a vmalloc virtual mapping The buggy address belongs to the physical page: Memory state around the buggy address: ffffd66320cf8780: 00 00 00 00 f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9 ffffd66320cf8800: 00 04 f9 f9 f9 f9 f9 f9 00 04 f9 f9 f9 f9 f9 f9 >ffffd66320cf8880: 00 00 00 00 00 00 00 00 00 00 00 00 f9 f9 f9 f9 ^ ffffd66320cf8900: 00 01 f9 f9 f9 f9 f9 f9 00 06 f9 f9 f9 f9 f9 f9 ffffd66320cf8980: 00 00 02 f9 f9 f9 f9 f9 00 00 02 f9 f9 f9 f9 f9 ================================================================== Commit 7915d7d5407c ("clk: amlogic: gxbb: drop non existing 32k clock parent") dropped a non-existing clock parent from the gxbb_32k_clk_sel mux but didn't adjust the hard-coded num_parents field. Fix the actual number of parents of that mux by using ARRAY_SIZE instead (avoiding similar problems in future).

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux f95e0f36e592e17a24ba4f56c355946448f84291 <8b2f7a411e7ceaef268355c2150c22ee3f509c3b; f18b09c998002ed6a67d1a235f3941a2662f1036; 5.4.292 <5.5; 4d32504f7ae951600e216aac4e04c81b02421a9d <f6ff0e6995dbff5cb145d7795c8f0af9c168094a; 6.15; 6.13.11 <6.14; 5.10.236 <5.10.270; patch: 7.2.5; patch: 6.18.51; 6.14.2 <6.15; 5.15.180 <5.15.221; b9778cd803b330b8d7a9b523743c35093454b77f <c86214e6178c38a0eff39110a4e92b824f5dd403; 1eb7a2f3e25075b2dc9b10c94616b066f80e79ee; 7061afacc89dec3f02f7412653b83f148a0c646b <404079d124d75a5da16322acc53d3ffc50b4ec68; patch: 5.15.221; 6ded8c22af4700bbf91da24ac025f9d05b879267 <1e509a6707d2fd9da79bdfa24742661b34562bfd; 6.12.23 <6.12.110; 7915d7d5407c026fa9343befb4d3343f7a345f97 <628b6fee9fca292f12d07f0f1bcf1edefa949d81; patch: 0; 6.6.87 <6.6.157; 450a1d9eac98886c7d19586dd10e72a4eaf8e1bc; patch: 6.6.157; patch: 6.1.188; patch: 7.3-rc1; 7915d7d5407c026fa9343befb4d3343f7a345f97 <4582949b7badcb91bb537ca522d69b8a35131e72; patch: 6.12.110; patch: 5.10.270; 7915d7d5407c026fa9343befb4d3343f7a345f97 <bf85bd6e550c17ffa585606fcc18eb5b7c95bbce; 6.1.134 <6.1.188

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.