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-64503iio: accel: kxsd9: fix runtime PM imbalance on write_raw() error

Description

In the Linux kernel, the following vulnerability has been resolved: iio: accel: kxsd9: fix runtime PM imbalance on write_raw() error kxsd9_write_raw() takes a runtime PM reference with pm_runtime_get_sync() but returns -EINVAL directly when a scale with a non-zero integer part is requested, skipping the matching pm_runtime_put_autosuspend(). This leaks a runtime PM usage-counter reference on every such write, after which the device can no longer autosuspend. Set the error code and fall through to the existing put instead of returning early.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months 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 (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 9a9a369d6178dd4e263c49085ce1b37e1e8f63a0 – < a93fd69c1ab0854ac4f5b8439c26dfadb25dfd20
    • affected 9a9a369d6178dd4e263c49085ce1b37e1e8f63a0 – < eeece4a85ece6f3837c75ef26a9b2bf5a1d0fcfc
    • affected 9a9a369d6178dd4e263c49085ce1b37e1e8f63a0 – < 191fcfeb729ededd8dd2a999c6bf351ddfa0cec7
    • affected 9a9a369d6178dd4e263c49085ce1b37e1e8f63a0 – < 36154171385a8a2444a4b3c6eaa0c5294cb02478
    • affected 9a9a369d6178dd4e263c49085ce1b37e1e8f63a0 – < 223703d6e8bed50b6a0b47e160877909518d94b9
    • affected 9a9a369d6178dd4e263c49085ce1b37e1e8f63a0 – < 6293211d142605bec435229ef0aa3668b8964164
    • affected 9a9a369d6178dd4e263c49085ce1b37e1e8f63a0 – < 13a91e8631cfeb68e5b7fd6687f194f5a86e83fe
    • affected 9a9a369d6178dd4e263c49085ce1b37e1e8f63a0 – < 44a5fd874bb6873bdaec59f722c1d57832fbc9df
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.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-64503 badge
[![CVE-2026-64503](https://cveledger.app/badge/CVE-2026-64503.svg)](https://cveledger.app/cve/CVE-2026-64503)

Record last updated .