Quick answers
- Is CVE-2026-98674 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98674 being exploited in the wild.
- How severe is CVE-2026-98674?
- Informational severity, published 18 October 2026.
- Which products and versions are affected?
- Unknown Linux kernel all versions with adi-axi-adc driver from commit 7ecb8ee5c93b onwards.
- Is there a fix for CVE-2026-98674?
- A patch was published on 2026-08-31: upstream fix merged Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-98674 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98674?
- 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 adi-axi-adc driver in drivers/iio/adc/adi-axi-adc.c uses st->lock mutex to serialize register access paths, but the probe function neglected to initialize this mutex before registering the device backend. An uninitialized mutex can result in unpredictable locking behavior, race conditions, and potential kernel memory corruption when concurrent operations occur.
Affected products
- <UNKNOWN> Linux kernel all versions with adi-axi-adc driver from commit 7ecb8ee5c93b onwards
Timeline
- 2026-10-18: disclosed
- 2026-08-31: patched: upstream fix merged