Is CVE-2026-98093 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-98093 being exploited in the wild.

How severe is CVE-2026-98093?

Informational severity, published 25 September 2026.

Which products and versions are affected?

Unknown Linux kernel Multiple kernel versions (likely 5.x and 6.x series based on git log).

Is there a fix for CVE-2026-98093?

A patch was published on 2026-09-01: Fix committed upstream by Mark Brown Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-98093 attacked?

It is attacked with local access, in an operating system.

Am I affected by CVE-2026-98093?

Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-98093: Linux kernel fsl_micfil clock enable/disable imbalance

CVE-2026-98093 · Severity: info · Published 2026-09-25

The Linux kernel's ALSA audio driver for Freescale microphones (fsl_micfil) improperly manages clock enable/disable calls, allowing the hardware clock to become stuck enabled or triggering false warnings. An application requesting audio hardware configuration multiple times or in unexpected orders can leave the audio clock ungated, potentially affecting system power management and other audio operations.

Technologies: Unknown Linux kernel. Vendors: Unknown.

Quick answers

Is CVE-2026-98093 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-98093 being exploited in the wild.
How severe is CVE-2026-98093?: Informational severity, published 25 September 2026.
Which products and versions are affected?: Unknown Linux kernel Multiple kernel versions (likely 5.x and 6.x series based on git log).
Is there a fix for CVE-2026-98093?: A patch was published on 2026-09-01: Fix committed upstream by Mark Brown Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-98093 attacked?: It is attacked with local access, in an operating system.
Am I affected by CVE-2026-98093?: Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The hw_params() callback unconditionally enables the mclk (master clock) and hw_free() unconditionally disables it, but the PCM core does not guarantee 1:1 pairing: hw_free() may execute without hw_params(), and hw_params() can be called multiple times from SETUP state. This causes a spurious "already disabled" warning and leaks enable references, leaving the clock ungateable. The fix guards both operations with an existing mclk_flag boolean to track actual enable state.

Affected products

<UNKNOWN> Linux kernel Multiple kernel versions (likely 5.x and 6.x series based on git log)

Timeline

2026-09-25: disclosed: Published in NVD
2026-09-01: patched: Fix committed upstream by Mark Brown
2026-09-21: patched: Fix included in stable kernel release

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.