Quick answers
- Is CVE-2026-98678 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98678 being exploited in the wild.
- How severe is CVE-2026-98678?
- Informational severity, published 18 October 2026.
- Which products and versions are affected?
- Unknown Linux kernel affected versions prior to fix commit d615210564205993e8f0e7ccb57cc2e66b7d5706.
- Is there a fix for CVE-2026-98678?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-98678 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98678?
- 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 ad4030_set_avg_frame_len() function in the AD4030 ADC driver computed ilog2() on user-supplied input before validating that the value was strictly positive, leading to undefined behavior. The fix moves input validation before the logarithm calculation to reject values less than 1. This is a local logic error with no network attack vector, triggered through the sysfs interface or iio subsystem.
Affected products
- <UNKNOWN> Linux kernel affected versions prior to fix commit d615210564205993e8f0e7ccb57cc2e66b7d5706
Timeline
- 2026-10-18: disclosed