CVE-2026-98848

rtc: ac100: Assign .num before accessing .hws

Description

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.

Key facts

Published
18 Oct 2026
Last changed
21 Oct 2026
Assigned by
Linux
EPSS
0.157% likely to be exploited in the next 30 days, higher than 4.913% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • f316cdff8d677db9ad9c90acb44c4cd535b0ee27 up to but excluding e77c5fc1f39fdb06ecd1f55b101eea1e1db2ffef (affected)
  • f316cdff8d677db9ad9c90acb44c4cd535b0ee27 up to but excluding 6bb55381daf1a1bed0657189a1396e7467712525 (affected)
  • f316cdff8d677db9ad9c90acb44c4cd535b0ee27 up to but excluding 160619b38707241e22569f9c983a4b3d0890996a (affected)
  • f316cdff8d677db9ad9c90acb44c4cd535b0ee27 up to but excluding ad1bf77039cba83373bf1eff3784655e3e3ed2ab (affected)
  • f316cdff8d677db9ad9c90acb44c4cd535b0ee27 up to but excluding 6a4117eee82dd85f11bf898bf66026764011eeb6 (affected)
LinuxLinux
  • Default status: affected
  • 6.6 (affected)
  • 0 up to but excluding 6.6 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.113 up to and including 6.12.* (unaffected)
  • 6.18.56 up to and including 6.18.* (unaffected)
  • 7.2.10 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 18 Oct 2026 Published

References