CVE-2026-98848

Vulnérabilité non évaluée dans Linux (Linux)

CVSS 0.0 · Non évaluée
EPSS 0.2%
Linux•Linux•Versions : 7.2.10, <160619b38707241e22569f9c983a4b3d0890996a, f316cdff8d677db9ad9c90acb44c4cd535b0ee27, 6.6, <=6.12.*, <=*, 6.18.56, <6.6, <6a4117eee82dd85f11bf898bf66026764011eeb6, <=6.18.*, 7.3, 0, <ad1bf77039cba83373bf1eff3784655e3e3ed2ab, <=7.2.*, <6bb55381daf1a1bed0657189a1396e7467712525, 6.12.113

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.

Gravité et risque d'exploitation

CVE-2026-98848 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.16 %, ce qui la place devant 4.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions 7.2.10, <160619b38707241e22569f9c983a4b3d0890996a, f316cdff8d677db9ad9c90acb44c4cd535b0ee27, 6.6, <=6.12.*, <=*, 6.18.56, <6.6, <6a4117eee82dd85f11bf898bf66026764011eeb6, <=6.18.*, 7.3, 0, <ad1bf77039cba83373bf1eff3784655e3e3ed2ab, <=7.2.*, <6bb55381daf1a1bed0657189a1396e7467712525, 6.12.113) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références