CVE-2026-64497: iio: chemical: scd30: Cleanup initializations and fix sign-extension bug
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 0ccff849bde90973e6c13a666f6ceab5c55b30d4, 1821bcacd8ac5b214c53be16cbb8172bf193f0b6, 40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598.
Low priority for now. Upgrade to Linux Linux 0ccff849bde90973e6c13a666f6ceab5c55b30d4, 1821bcacd8ac5b214c53be16cbb8172bf193f0b6, 40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.9affected
- 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and later · before 0ccff849bde90973e6c13a666f6ceab5c55b30d4affected · git
- 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and later · before 1821bcacd8ac5b214c53be16cbb8172bf193f0b6affected · git
- 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and later · before 40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598affected · git
- 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and later · before b131f0011dfef72350f4e3f11df94dc3e6b46065affected · git
- 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and later · before 8d4a46e971cf846bda98b20d4cabfa21c1276e5faffected · git
- 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and later · before 82accdd57404399eddf3d56fd9beda7c61307388affected · git
- 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and later · before d49ff54b2784aa56a7c97982de713604de89d23aaffected · git
- 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 and later · before 60d877910a43c305b5165131b258a17b1d772d57affected · git
- before 5.9not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-64495Jul 25, 2026 · iio: gyro: bmg160: bail out when bandwidth/filter is not in table0Monitor
- ← EarlierCVE-2026-64496Jul 25, 2026 · iio: event: Fix event FIFO reset race28Monitor
- Later →CVE-2026-64498Jul 25, 2026 · iio: buffer: hw-consumer: free scan_mask on buffer release0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ccff849bde90973e6c13a666f6ceab5c55b30d4 | Vendor (CNA) |
| Linux Linux | 1821bcacd8ac5b214c53be16cbb8172bf193f0b6 | Vendor (CNA) |
| Linux Linux | 40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598 | Vendor (CNA) |
| Linux Linux | 60d877910a43c305b5165131b258a17b1d772d57 | Vendor (CNA) |
| Linux Linux | 82accdd57404399eddf3d56fd9beda7c61307388 | Vendor (CNA) |
| Linux Linux | 8d4a46e971cf846bda98b20d4cabfa21c1276e5f | Vendor (CNA) |
| Linux Linux | b131f0011dfef72350f4e3f11df94dc3e6b46065 | Vendor (CNA) |
| Linux Linux | d49ff54b2784aa56a7c97982de713604de89d23a | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1821bcacd8ac5b214c53be16cbb8172bf193f0b6
- git.kernel.org/stable/c/40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598
- git.kernel.org/stable/c/60d877910a43c305b5165131b258a17b1d772d57
- git.kernel.org/stable/c/82accdd57404399eddf3d56fd9beda7c61307388
- git.kernel.org/stable/c/8d4a46e971cf846bda98b20d4cabfa21c1276e5f
- git.kernel.org/stable/c/b131f0011dfef72350f4e3f11df94dc3e6b46065
- git.kernel.org/stable/c/d49ff54b2784aa56a7c97982de713604de89d23a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.