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-97969watchdog: msc313e: Fix clock leak and spurious timer in settimeout()

Description

In the Linux kernel, the following vulnerability has been resolved: watchdog: msc313e: Fix clock leak and spurious timer in settimeout() msc313e_wdt_settimeout() unconditionally calls msc313e_wdt_start() which introduces two severe bugs: 1. If the watchdog is already active, calling start() again will increase the reference count of the clock again. However stop() is only called once, the reference count is unbalance. 2. If the watchdog is stopped, calling settimeout() will start the hardware timer accidentally. Factor out the register-writing logic into a helper function. Only call it in settimeout() if the watchdog is running. Otherwise, simply update `wdev->timeout`.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 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.17% · top 93% of all CVEs (13 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 e9800b7994642a794afd4894f072541c14277ce8 – < 68665016c7b777b44e27b6b0c1e6524c28ebe40a
    • affected e9800b7994642a794afd4894f072541c14277ce8 – < 77ef2aa8b46876ca9935f32dd874c517ccf5d880
    • affected e9800b7994642a794afd4894f072541c14277ce8 – < a1dd0817776ea2a870ba2347001af13ddd4cb321
    • affected e9800b7994642a794afd4894f072541c14277ce8 – < 2152a13ee2a9af09a668ebd053a8dbf771dadb80
    • affected e9800b7994642a794afd4894f072541c14277ce8 – < 2abf99a57b0b71b2b97745981f4039370ab78044
    • affected e9800b7994642a794afd4894f072541c14277ce8 – < faf1eb2895c87a8c0fb920439dddc7e0d97c6a69
    • affected e9800b7994642a794afd4894f072541c14277ce8 – < 3db30f315935c2fb0d95f46b7a593b5b4d3ec3d0
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .