CVE-2026-98672 Linux CVE debrief

Who should care

Linux kernel maintainers and users, particularly those using the stm32-adc component, should verify their kernel versions and apply patches to prevent division by zero errors. This includes verifying kernel versions, checking for errors or zero values before processing data in iio: adc: stm32-adc, and monitoring Linux kernel updates for fixes. Additionally, security teams and vulnerability management teams should be aware of this vulnerability and its

Why it matters

A vulnerability in the Linux kernel's iio: adc: stm32-adc component can lead to a division by zero when processing channel data. This occurs if the conversion fails or returns zero. The issue arises from inadequate error checking before processing the converted value.

• Verify Linux kernel versions to ensure patch application
• Check for errors or zero values before processing data in iio: adc: stm32-adc
• Monitor Linux kernel updates for fixes

Technical summary

The Linux kernel's iio: adc: stm32-adc component is vulnerable to a division by zero error when processing channel data. This occurs if the conversion fails or returns zero. The issue arises from inadequate error checking before processing the converted value. Specifically, the Vrefint channel returns a zero value, which should be considered invalid. To address this, it's essential to check for errors or zero values before processing the data. Linux kernel maintainers and users, particularly those using the stm32-adc component, should verify their kernel versions and apply patches to prevent division by zero errors.

Defensive priority

Verify Linux kernel versions and apply patches to prevent division by zero errors in iio: adc: stm32-adc.

Recommended defensive actions

• Verify Linux kernel versions and apply patches
• Check for errors or zero values before processing data in iio: adc: stm32-adc
• Monitor Linux kernel updates for fixes
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. However, specific version information and exploitation details are not provided. Linux kernel maintainers and users should verify their kernel versions and apply patches to prevent division by zero errors. The vulnerability arises from inadequate error checking before processing the converted value in the iio: adc: stm32-adc component. To address this, it's essential to check for errors or zero values before processing the data. The Vrefint channel returns a zero value

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.