Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99089ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM

Description

In the Linux kernel, the following vulnerability has been resolved: ASoC: samsung: i2s: enable op_clk in probe to balance runtime PM The probe function puts the device into the runtime PM active state with only the "iis" bus clock enabled, but it also sets priv->op_clk to the parent of the RCLK_SRC mux without enabling it. The runtime PM suspend callback disables both clocks, so the first runtime suspend after probe disables op_clk once more than it was enabled. On Exynos5250 Arndale both clocks resolve to the same EXYNOS_I2S_BUS gate, so this triggers the following warning during boot: WARNING: drivers/clk/clk.c:1270 at clk_core_disable+0xe4/0x23c, CPU#0: kworker/u8:3/45 i2s_bus already disabled ... Workqueue: pm pm_runtime_work Call trace: ... clk_core_disable from clk_disable+0x28/0x34 clk_disable from i2s_runtime_suspend+0x58/0x68 [snd_soc_i2s] i2s_runtime_suspend [snd_soc_i2s] from genpd_runtime_suspend+0xc4/0x298 genpd_runtime_suspend from __rpm_callback+0x48/0x18c __rpm_callback from rpm_callback+0x4c/0x50 rpm_callback from rpm_suspend+0xf4/0x718 rpm_suspend from pm_runtime_work+0x9c/0xa0 ... Fix this by enabling op_clk in probe right after getting it, so the clock state matches the runtime PM active state, and by disabling it in remove.

Timeline

  1. ID reserved

    By Linux

  2. · 31 days later

    Published

  3. · 4 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b – < 09cda41564966c7f9d2a5fa7022af18b5d4161be
    • affected 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b – < 004c8ec5d71c01b93284042f1174b70cf1390e59
    • affected 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b – < 05d79040b7ebd46862c4bf4864d373dad8b6fecb
    • affected 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b – < 2c64c30d493d82d5edc95811cede0083e1195822
    • affected 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b – < 5dac6bf09b5a4fff2433629801309c3884c3e94a
    • affected 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b – < 64bb35079dcbc67901da1fe8c52c234cbcd17df3
    • affected 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b – < a728c12f8bd89947894e227d0f4f83a895ac9ab7
    • affected 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b – < 7529254014764ae0b8c33d5c61a58f36c65b1a1c
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99089 badge
[![CVE-2026-99089](https://cveledger.app/badge/CVE-2026-99089.svg)](https://cveledger.app/cve/CVE-2026-99089)

Record last updated .