Skip to content
Heist/ feed
Back to feed
UnratedFix available

clk: samsung: exynos-clkout: Assign .num before accessing .hws

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: clk: samsung: exynos-clkout: 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 exynos_clkout_probe() due to .num being assigned after .hws[] has been accessed: UBSAN: array-index-out-of-bounds in drivers/clk/samsung/clk-exynos-clkout.c:178:18 index 0 is out of range for type 'clk_hw *[*]' Move the .num initialization to before the first access of .hws[], clearing up the warning.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.64, 6.18.4, 6.6.120
CVEs
CVE-2025-71143
Confirmed fixed CVEs
Not specified
Updated in this feed
4 Nov 2026, 16:15 UTC · Revision 1

Source evidence

clk: samsung: exynos-clkout: Assign .num before accessing .hws

core-osv · Original source

Published 14 Jan 2026, 15:07 UTC

In the Linux kernel, the following vulnerability has been resolved: clk: samsung: exynos-clkout: 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 exynos_clkout_probe() due to .num being assigned after .hws[] has been accessed: UBSAN: array-index-out-of-bounds in drivers/clk/samsung/clk-exynos-clkout.c:178:18 index 0 is out of range for type 'clk_hw *[*]' Move the .num initialization to before the first access of .hws[], clearing up the warning.

osv:CVE-2025-71143

Kernel

Fixed versions: 6.6.120, 6.12.64, 6.18.4

Complete source record
{
  "id": "73b009eaee9cddb069a74efa32dcfc7a35756e56a9ddf744bcd007457e440454",
  "url": "https://osv.dev/vulnerability/CVE-2025-71143",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "clk: samsung: exynos-clkout: Assign .num before accessing .hws",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: clk: samsung: exynos-clkout: 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 exynos_clkout_probe() due to .num being assigned after .hws[] has been accessed: UBSAN: array-index-out-of-bounds in drivers/clk/samsung/clk-exynos-clkout.c:178:18 index 0 is out of range for type 'clk_hw *[*]' Move the .num initialization to before the first access of .hws[], clearing up the warning.",
    "evidence": "osv:CVE-2025-71143",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.6.120",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.64",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.4",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2025-71143",
      "aliases": [
        "CVE-2025-71143"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "f316cdff8d677db9ad9c90acb44c4cd535b0ee27"
                },
                {
                  "fixed": "fbf57f5e453dadadb3d29b2d1dbe067e3dc4e236"
                },
                {
                  "fixed": "eb1f3a6ab3efee2b52361879cdc2dc6b11f499c0"
                },
                {
                  "fixed": "a317f63255ebc3dac378c79c5bff4f8d0561c290"
                },
                {
                  "fixed": "cf33f0b7df13685234ccea7be7bfe316b60db4db"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71143.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.6.0"
                },
                {
                  "fixed": "6.6.120"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.64"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.4"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71143.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:37.606429986Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/a317f63255ebc3dac378c79c5bff4f8d0561c290",
        "https://git.kernel.org/stable/c/cf33f0b7df13685234ccea7be7bfe316b60db4db",
        "https://git.kernel.org/stable/c/eb1f3a6ab3efee2b52361879cdc2dc6b11f499c0",
        "https://git.kernel.org/stable/c/fbf57f5e453dadadb3d29b2d1dbe067e3dc4e236",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71143.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-71143",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71143.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-71143",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 504584,
  "published_at": "2026-01-14T15:07:55.828+00:00"
}