GHSA-8JGG-JGF5-2V4Q
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 15:31In 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).
{
"affected": [],
"aliases": [
"CVE-2026-89947"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:17:04Z",
"severity": "HIGH"
},
"details": "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\u0027t 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).",
"id": "GHSA-8jgg-jgf5-2v4q",
"modified": "2026-09-16T15:31:03Z",
"published": "2026-09-16T12:30:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89947"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1e509a6707d2fd9da79bdfa24742661b34562bfd"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/404079d124d75a5da16322acc53d3ffc50b4ec68"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4582949b7badcb91bb537ca522d69b8a35131e72"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/628b6fee9fca292f12d07f0f1bcf1edefa949d81"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8b2f7a411e7ceaef268355c2150c22ee3f509c3b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/bf85bd6e550c17ffa585606fcc18eb5b7c95bbce"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c86214e6178c38a0eff39110a4e92b824f5dd403"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f6ff0e6995dbff5cb145d7795c8f0af9c168094a"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H",
"type": "CVSS_V3"
}
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.