Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Fixed version: Linux Linux 004c8ec5d71c01b93284042f1174b70cf1390e59, 05d79040b7ebd46862c4bf4864d373dad8b6fecb, 09cda41564966c7f9d2a5fa7022af18b5d4161be.

Low priority for now. Upgrade to Linux Linux 004c8ec5d71c01b93284042f1174b70cf1390e59, 05d79040b7ebd46862c4bf4864d373dad8b6fecb, 09cda41564966c7f9d2a5fa7022af18b5d4161be or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 26, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 6th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99089

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.17affected
    • 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b and later · before 09cda41564966c7f9d2a5fa7022af18b5d4161beaffected · git
    • 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b and later · before 004c8ec5d71c01b93284042f1174b70cf1390e59affected · git
    • 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b and later · before 05d79040b7ebd46862c4bf4864d373dad8b6fecbaffected · git
    • 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b and later · before 2c64c30d493d82d5edc95811cede0083e1195822affected · git
    • 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b and later · before 5dac6bf09b5a4fff2433629801309c3884c3e94aaffected · git
    • 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b and later · before 64bb35079dcbc67901da1fe8c52c234cbcd17df3affected · git
    • 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b and later · before a728c12f8bd89947894e227d0f4f83a895ac9ab7affected · git
    • 48279c53fd1d09dc0d1b6ebb9f21732c507cea0b and later · before 7529254014764ae0b8c33d5c61a58f36c65b1a1caffected · git
    • before 4.17not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.11-17.2.11-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99087Oct 23, 2026 · dm-integrity: fix NULL pointer dereference when the 'R' flag is used
    0Monitor
  • ← EarlierCVE-2026-99088Oct 26, 2026 · net: openvswitch: validate transport header presence in set_ipv6_addr
    0Monitor
  • Later →CVE-2026-99090Oct 26, 2026 · drm/amdgpu: serialize vblank counter reads against GPU reset
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux004c8ec5d71c01b93284042f1174b70cf1390e59Vendor (CNA)
Linux Linux05d79040b7ebd46862c4bf4864d373dad8b6fecbVendor (CNA)
Linux Linux09cda41564966c7f9d2a5fa7022af18b5d4161beVendor (CNA)
Linux Linux2c64c30d493d82d5edc95811cede0083e1195822Vendor (CNA)
Linux Linux5dac6bf09b5a4fff2433629801309c3884c3e94aVendor (CNA)
Linux Linux64bb35079dcbc67901da1fe8c52c234cbcd17df3Vendor (CNA)
Linux Linux7529254014764ae0b8c33d5c61a58f36c65b1a1cVendor (CNA)
Linux Linuxa728c12f8bd89947894e227d0f4f83a895ac9ab7Vendor (CNA)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 5, 2026+10 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records