# clk: samsung: Fix UBSAN panic in samsung_clk_init()

CVE record · `CVE-2025-39728`

- **Identifiers:** `CVE-2025-39728`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-129](https://cwe.mitre.org/data/definitions/129.html)
- **Tags:** [CWE-129](https://agentprime.io/advisories/tag/cwe-129.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 18 Apr 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 18 Apr 2025, 07:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `e620a1e061c4738e26c3edf2abaae7842532cd80 to before 00307934eb94aaa0a99addfb37b9fe206f945004` (git)
  - affected: `e620a1e061c4738e26c3edf2abaae7842532cd80 to before d974e177369c034984cece9d7d4fada9f8b9c740` (git)
  - affected: `e620a1e061c4738e26c3edf2abaae7842532cd80 to before 0fef48f4a70e45a93e73c39023c3a6ea624714d6` (git)
  - affected: `e620a1e061c4738e26c3edf2abaae7842532cd80 to before 4d29a6dcb51e346595a15b49693eeb728925ca43` (git)
  - affected: `e620a1e061c4738e26c3edf2abaae7842532cd80 to before 24307866e0ac0a5ddb462e766ceda5e27a6fbbe3` (git)
  - affected: `e620a1e061c4738e26c3edf2abaae7842532cd80 to before a1500b98cd81a32fdfb9bc63c33bb9f0c2a0a1bf` (git)
  - affected: `e620a1e061c4738e26c3edf2abaae7842532cd80 to before 157de9e48007a20c65d02fc0229a16f38134a72d` (git)
  - affected: `e620a1e061c4738e26c3edf2abaae7842532cd80 to before d19d7345a7bcdb083b65568a11b11adffe0687af` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.5`
  - unaffected: `before 5.5` (semver)
  - unaffected: `5.10.236 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.180 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.134 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.87 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.23 to 6.12.*, inclusive` (semver)
  - unaffected: `6.13.11 to 6.13.*, inclusive` (semver)
  - unaffected: `6.14.2 to 6.14.*, inclusive` (semver)
  - unaffected: `6.15 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 18 Apr 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2025-39728](https://www.cve.org/CVERecord?id=CVE-2025-39728)
- [NVD: CVE-2025-39728](https://nvd.nist.gov/vuln/detail/CVE-2025-39728)

### References from the CNA

- <https://git.kernel.org/stable/c/00307934eb94aaa0a99addfb37b9fe206f945004>
- <https://git.kernel.org/stable/c/d974e177369c034984cece9d7d4fada9f8b9c740>
- <https://git.kernel.org/stable/c/0fef48f4a70e45a93e73c39023c3a6ea624714d6>
- <https://git.kernel.org/stable/c/4d29a6dcb51e346595a15b49693eeb728925ca43>
- <https://git.kernel.org/stable/c/24307866e0ac0a5ddb462e766ceda5e27a6fbbe3>
- <https://git.kernel.org/stable/c/a1500b98cd81a32fdfb9bc63c33bb9f0c2a0a1bf>
- <https://git.kernel.org/stable/c/157de9e48007a20c65d02fc0229a16f38134a72d>
- <https://git.kernel.org/stable/c/d19d7345a7bcdb083b65568a11b11adffe0687af>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-39728>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-39728/>. Everything for agents: <https://agentprime.io/llms.txt>.