Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 23 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Awaiting Analysis.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 – < 0ccff849bde90973e6c13a666f6ceab5c55b30d4
    • affected 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 – < 1821bcacd8ac5b214c53be16cbb8172bf193f0b6
    • affected 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 – < 40bb0fdb37f441c9c9f52bf58bbd8a0ca3cc9598
    • affected 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 – < b131f0011dfef72350f4e3f11df94dc3e6b46065
    • affected 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 – < 8d4a46e971cf846bda98b20d4cabfa21c1276e5f
    • affected 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 – < 82accdd57404399eddf3d56fd9beda7c61307388
    • affected 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 – < d49ff54b2784aa56a7c97982de713604de89d23a
    • affected 64b3d8b1b0f5c16c19045785e4da8391ae35ec99 – < 60d877910a43c305b5165131b258a17b1d772d57
  • Linux · Linux

    • affected 5.9
    • unaffected < 5.9
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64497 badge
[![CVE-2026-64497](https://cveledger.app/badge/CVE-2026-64497.svg)](https://cveledger.app/cve/CVE-2026-64497)

Record last updated .