rtc: ac100: Assign .num before accessing .hws
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.113, 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: rtc: ac100: Assign .num before accessing .hws Commit f316cdff8d67 ("clk: Annotate struct clk_hw_onecell_data with __counted_by") annotated the hws member of 'struct clk_hw_onecell_data' with __counted_by, which informs the bounds sanitizer (UBSAN_BOUNDS) about the number of elements in .hws[], so that it can warn when .hws[] is accessed out of bounds. As noted in that change, the __counted_by member must be initialized with the number of elements before the first array access happens, otherwise there will be a warning from each access prior to the initialization because the number of elements is zero. This occurs in ac100_rtc_register_clks() due to .num being assigned only after every clkout clock has been stored in .hws[]. With CONFIG_UBSAN_BOUNDS and a compiler that implements __counted_by (GCC 15.1+ or Clang 20.1+), this triggers an array-index-out-of-bounds report during probe, and with CONFIG_UBSAN_TRAP the first store traps. Initialize .num with AC100_CLKOUT_NUM, the number of elements .hws[] was allocated with, right after the allocation. That is the value the loop counter ends up at on the success path anyway, so the provider's behaviour is unchanged.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From f316cdff8d677db9ad9c90acb44c4cd535b0ee27 · fixed in e77c5fc1f39fdb06ecd1f55b101eea1e1db2ffef; From f316cdff8d677db9ad9c90acb44c4cd535b0ee27 · fixed in 6bb55381daf1a1bed0657189a1396e7467712525; From f316cdff8d677db9ad9c90acb44c4cd535b0ee27 · fixed in 160619b38707241e22569f9c983a4b3d0890996a; From f316cdff8d677db9ad9c90acb44c4cd535b0ee27 · fixed in ad1bf77039cba83373bf1eff3784655e3e3ed2ab; From f316cdff8d677db9ad9c90acb44c4cd535b0ee27 · fixed in 6a4117eee82dd85f11bf898bf66026764011eeb6
- Linux Linux
6.6
- KernelLinux
From 6.6.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10