# CVE-2026-98410: watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog

> A flaw in the Linux kernel da9063 watchdog driver causes unexpected system resets during suspend due to improper state handling.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-108182, BELL-CVE-2026-98410, DEBIAN-CVE-2026-98410, GHSA-v9jm-64rh-hf94, UBUNTU-CVE-2026-98410

## What is CVE-2026-98410?

CVE-2026-98410 is a denial of service vulnerability in Linux, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98410?


## How do I fix CVE-2026-98410?

Apply the vendor's patch.

## Is CVE-2026-98410 being exploited?

There is no known exploitation of CVE-2026-98410 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98410 and fix it if it is affected.

What it is: CVE-2026-98410 is a denial of service vulnerability in Linux, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98410 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98410/ (Markdown: https://insights.sbomify.com/CVE-2026-98410/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98410
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98410
- OSV: https://osv.dev/vulnerability/CVE-2026-98410

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98410/
Summaries are generated and may contain mistakes; the official description above is the record.