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-98679iio: accel: kxcjk-1013: reject duplicate event disable

Description

In the Linux kernel, the following vulnerability has been resolved: iio: accel: kxcjk-1013: reject duplicate event disable The IIO core does not filter duplicate writes to the event enable attribute. kxcjk1013_write_event_config() already ignores repeated enable requests, but a repeated disable request still calls kxcjk1013_set_power_state(data, false), dropping a runtime PM reference that was not acquired for this request. This can underflow the runtime PM usage count and trigger a "Runtime PM usage count underflow" warning. Return early when the requested state already matches ev_enable_state.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 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: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (14 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 b4b491c0832ef90a7a5070e5975bc8427f2049ca – < b33dfdc0f22dd6c9cb9ae34a32723ef0a5d2ccf5
    • affected b4b491c0832ef90a7a5070e5975bc8427f2049ca – < 8c6d1abaff5dbbe2d2b7529de7f1f2395a2f07e9
    • affected b4b491c0832ef90a7a5070e5975bc8427f2049ca – < 2f9f88da802733bab7a87a0e685c8cfa7488f6ac
    • affected b4b491c0832ef90a7a5070e5975bc8427f2049ca – < 137c35cff4d4d69f73cbfc0bf7870bf379a7a364
    • affected b4b491c0832ef90a7a5070e5975bc8427f2049ca – < ad690c0c1b9131725619e352cb7c970488cbf436
    • affected b4b491c0832ef90a7a5070e5975bc8427f2049ca – < 3365209e758c845a197211645731f0e393a86012
    • affected b4b491c0832ef90a7a5070e5975bc8427f2049ca – < aa94a37b5a3e560c277dac6f9e5d0d75549a6583
    • affected b4b491c0832ef90a7a5070e5975bc8427f2049ca – < dd30c10ff60d2b30386c23bb7c61cc97f2385c97
  • Linux · Linux

    • affected 3.18
    • unaffected < 3.18
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.56 – ≤ 6.18.*
    • unaffected 7.2.10 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .