Quick answers
- Is CVE-2026-98956 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98956 being exploited in the wild.
- How severe is CVE-2026-98956?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- Linux kernel 6.0 through 6.12 and earlier versions in stable branches.
- Is there a fix for CVE-2026-98956?
- A patch was published on 2026-10-06: Upstream commit 64dd172bbffe6135d79a06ddad53dd2da4d8bd62 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-98956 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98956?
- Check whether you run 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 vulnerability is a kernel warning (not a security flaw) in the ASoC ADAU1372 codec driver where gpiod_set_value() is called on a GPIO that may require sleeping (typical for I2C-controlled GPIO expanders). The fix replaces gpiod_set_value() with gpiod_set_value_cansleep() in the adau1372_set_power() function, which is called only in process context. This allows I2C GPIO expanders to be used for the powerdown GPIO without triggering kernel warnings.
Affected products
- Linux kernel 6.0 through 6.12 and earlier versions in stable branches
Timeline
- 2026-10-23: disclosed
- 2026-10-06: patched: Upstream commit 64dd172bbffe6135d79a06ddad53dd2da4d8bd62