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-68357watchdog: pretimeout: Fix UAF in watchdog_unregister_governor()

Description

In the Linux kernel, the following vulnerability has been resolved: watchdog: pretimeout: Fix UAF in watchdog_unregister_governor() When a watchdog governor is unregistered, it updates existing watchdog devices that were using this governor by falling back to `default_gov`. If the governor being unregistered is currently set as `default_gov`, the `default_gov` is never cleared. This leads to 2 use-after-free issues: 1. New watchdog devices registered after this point will inherit the dangling `default_gov`. 2. Existing watchdog devices using the unregistered governor will have their `wdd->gov` reassigned to the dangling `default_gov`. Fix the UAF by clearing `default_gov` if it matches the governor being unregistered.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 9 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 (16 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 da0d12ff2b829a35e9921918e925d79497b82bef – < b9ae33faa96bdec6bc60e4c5f8f53786182e4207
    • affected da0d12ff2b829a35e9921918e925d79497b82bef – < 472ec1e34ff0bb26379805cae808f658cce58c35
    • affected da0d12ff2b829a35e9921918e925d79497b82bef – < 7a2ee3ec6f208307eca1119a343c7b5d39c03708
    • affected da0d12ff2b829a35e9921918e925d79497b82bef – < 2e47b91b9b4020fcc01def14d6b6556d66074cf4
    • affected da0d12ff2b829a35e9921918e925d79497b82bef – < 0ca252720f0e38411cfec3431db9bb1aed0a412c
    • affected da0d12ff2b829a35e9921918e925d79497b82bef – < 7d1658b066de30f4b23afc14814d22416a971e6e
    • affected da0d12ff2b829a35e9921918e925d79497b82bef – < 7993d626983cc58fbde9607333cfd2d57725c197
    • affected da0d12ff2b829a35e9921918e925d79497b82bef – < 7362ba0f9c96ac3ad6a2ca3995bd9fc9a28a8661
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 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-68357 badge
[![CVE-2026-68357](https://cveledger.app/badge/CVE-2026-68357.svg)](https://cveledger.app/cve/CVE-2026-68357)

Record last updated .