CVE-2026-64497

iio: chemical: scd30: Cleanup initializations and fix sign-extension bug

N/A
Published: July 25, 2026 at 08:51 AM UTC
Updated: August 17, 2026 at 05:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: iio: chemical: scd30: Cleanup initializations and fix sign-extension bug Include linux/bitfield.h for FIELD_GET(). Create new macros for bit manipulation in combination with manual bit manipulation being replaced with FIELD_GET(). The current variable declaration and initializations are barely readable and use comma separations across multiple lines. Refactor the initializations so that mantissa and exp have separate declarations and sign gets initialized later. In addition (and due to the nature of the cleanup), fix a sign-extension bug where, float32 would get bitwise anded with ~BIT(31) (which is 0xFFFFFFFF7FFFFFFF) which corrupted the exponent.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.9 ≤ v < 5.10.2615.9 ≤ v < 5.15.2125.9 ≤ v < 6.1.1785.9 ≤ v < 6.12.965.9 ≤ v < 6.18.395.9 ≤ v < 6.6.1455.9 ≤ v < 7.1.45.9 ≤ v < 7.25.964b3d8b1b0f5c16c19045785e4da8391ae35ec99
Vendor states this is fixed in 0ccff849bde90973e6c13a666f6ceab5c55b30d4 (fixed)
Vendor states this is fixed in 1821bcacd8ac5b214c53be16cbb8172bf193f0b6 (fixed)
Vendor states this is fixed in 40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598 (fixed)
Vendor states this is fixed in 60d877910a43c305b5165131b258a17b1d772d57 (fixed)
Vendor states this is fixed in 82accdd57404399eddf3d56fd9beda7c61307388 (fixed)
Vendor states this is fixed in 8d4a46e971cf846bda98b20d4cabfa21c1276e5f (fixed)
Vendor states this is fixed in b131f0011dfef72350f4e3f11df94dc3e6b46065 (fixed)
Vendor states this is fixed in d49ff54b2784aa56a7c97982de713604de89d23a (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 5.9 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card