Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2026-68357

Published Aug 10, 2026 EPSS 0.18% (7th pctl)

Overview

CVE-2026-68357 is a known-severity vulnerability. It was published on August 10, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Ref git.kernel.org/stable/c/0ca252720f0e38411cfec3431db9bb1aed0a412c Ref git.kernel.org/stable/c/2e47b91b9b4020fcc01def14d6b6556d66074cf4 Ref git.kernel.org/stable/c/472ec1e34ff0bb26379805cae808f658cce58c35 Ref git.kernel.org/stable/c/7362ba0f9c96ac3ad6a2ca3995bd9fc9a28a8661 Ref git.kernel.org/stable/c/7993d626983cc58fbde9607333cfd2d57725c197 Ref git.kernel.org/stable/c/7a2ee3ec6f208307eca1119a343c7b5d39c03708 Ref git.kernel.org/stable/c/7d1658b066de30f4b23afc14814d22416a971e6e Ref git.kernel.org/stable/c/b9ae33faa96bdec6bc60e4c5f8f53786182e4207

Frequently Asked Questions

What is CVE-2026-68357?

CVE-2026-68357 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-68357?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-68357?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-68357?

CyberStrike's AI-powered security agents can automatically detect CVE-2026-68357 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.

How CyberStrike Helps

Autonomous Discovery

AI agents map your attack surface to find vulnerabilities like this one.
Continuous Pentesting

Automated penetration testing that runs continuously, not just quarterly.
Code Review

AI-driven PR review catches vulnerable dependencies before they ship.
HackBrowser

Browser-based exploitation validates findings with real proof-of-concept.
Browse by year 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999