CVE-2026-64497 — iio: chemical: scd30: Cleanup initializations and fix sign-extension bug
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- No scoring signals.
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and < 0ccff849bde90973e6c13a666f6ceab5c55b30d4≥ 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and < 1821bcacd8ac5b214c53be16cbb8172bf193f0b6≥ 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and < 40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598≥ 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and < b131f0011dfef72350f4e3f11df94dc3e6b46065≥ 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and < 8d4a46e971cf846bda98b20d4cabfa21c1276e5f≥ 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and < 82accdd57404399eddf3d56fd9beda7c61307388≥ 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and < d49ff54b2784aa56a7c97982de713604de89d23a≥ 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and < 60d877910a43c305b5165131b258a17b1d772d57 and 1 moreversion 5.9 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/0ccff849bde90973e6c13a666f6ceab5c55b30d4
- git.kernel.org/stable/c/60d877910a43c305b5165131b258a17b1d772d57
- git.kernel.org/stable/c/8d4a46e971cf846bda98b20d4cabfa21c1276e5f
- git.kernel.org/stable/c/40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598
- git.kernel.org/stable/c/b131f0011dfef72350f4e3f11df94dc3e6b46065
- git.kernel.org/stable/c/82accdd57404399eddf3d56fd9beda7c61307388
- git.kernel.org/stable/c/d49ff54b2784aa56a7c97982de713604de89d23a
- git.kernel.org/stable/c/1821bcacd8ac5b214c53be16cbb8172bf193f0b6
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 12h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 12h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-64497 is "iio: chemical: scd30: Cleanup initializations and fix sign-extension bug", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.