# CVE-2026-64497: iio: chemical: scd30: Cleanup initializations and fix sign-extension bug

> A sign-extension bug in the Linux kernel SCD30 sensor driver can corrupt data, potentially leading to information disclosure or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-64497, DEBIAN-CVE-2026-64497, GHSA-mrh8-mp34-58pv, ROOT-OS-UBUNTU-2204-CVE-2026-64497, UBUNTU-CVE-2026-64497

## What is CVE-2026-64497?

CVE-2026-64497 is a vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-64497?


## How do I fix CVE-2026-64497?

Apply the vendor's patch.

## Is CVE-2026-64497 being exploited?

There is no known exploitation of CVE-2026-64497 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64497 and fix it if it is affected.

What it is: CVE-2026-64497 is a vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64497 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64497/ (Markdown: https://insights.sbomify.com/CVE-2026-64497/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64497
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64497
- OSV: https://osv.dev/vulnerability/CVE-2026-64497

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64497/
Summaries are generated and may contain mistakes; the official description above is the record.