CVE-2026-98410
Last modified
CVE-2026-98410 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog da9063_wdt_suspend() and da9063_wdt_resume() only check watchdog_active(), when the watchdog is left running by the driver sets WDOG_HW_RUNNING in da9063_wdt_probe() but userspace never opens the device, so WDOG_ACTIVE remains cleared, the wdt_disable() will not be executed in da9063_wdt_suspend. In this case, the suspend callback is a no-op and the watchdog keeps counting during system suspend, leading to an unexpected system reset. Check WDOG_HW_RUNNING and wdd,can fix this issue..
Description
In the Linux kernel, the following vulnerability has been resolved: watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog da9063_wdt_suspend() and da9063_wdt_resume() only check watchdog_active(), when the watchdog is left running by the driver sets WDOG_HW_RUNNING in da9063_wdt_probe() but userspace never opens the device, so WDOG_ACTIVE remains cleared, the wdt_disable() will not be executed in da9063_wdt_suspend. In this case, the suspend callback is a no-op and the watchdog keeps counting during system suspend, leading to an unexpected system reset. Check WDOG_HW_RUNNING and wdd,can fix this issue.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a7ceca4398bc835c6ad29d10e1106de4cf0332e1, < 95adc37f47cdf5a5285f7163b24243680af510be; >= a7ceca4398bc835c6ad29d10e1106de4cf0332e1, < c30b419c7e6fbe31c48a44c828174168b732dc5b; >= a7ceca4398bc835c6ad29d10e1106de4cf0332e1, < 1c42e39b0990371b9d76ae22c3f33eb6df341251; >= a7ceca4398bc835c6ad29d10e1106de4cf0332e1, < 960d1c85381bcaae866dd799b1c905ec5d39ebce; >= a7ceca4398bc835c6ad29d10e1106de4cf0332e1, < 1db134d0d2a51a136296584854570e5e04adedb0; >= a7ceca4398bc835c6ad29d10e1106de4cf0332e1, < 7cb575b71ab98194d2e040bded3a7281e089c5ed |
| Linux | Linux | 5.19 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98410?
How severe is CVE-2026-98410?
How do I fix CVE-2026-98410?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98404In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98405In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98406In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98407In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98408In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98409In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98411In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98412In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98413In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98414In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98415In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98416In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98410?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
