CVE-2026-98410: watchdog: da9063: fix suspend/resume handling of HW_RUNNING watchdog
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 1c42e39b0990371b9d76ae22c3f33eb6df341251, 1db134d0d2a51a136296584854570e5e04adedb0, 7cb575b71ab98194d2e040bded3a7281e089c5ed.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1c42e39b0990371b9d76ae22c3f33eb6df341251, 1db134d0d2a51a136296584854570e5e04adedb0, 7cb575b71ab98194d2e040bded3a7281e089c5ed or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 14, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.19affected
- a7ceca4398bc835c6ad29d10e1106de4cf0332e1 and later · before 95adc37f47cdf5a5285f7163b24243680af510beaffected · git
- a7ceca4398bc835c6ad29d10e1106de4cf0332e1 and later · before c30b419c7e6fbe31c48a44c828174168b732dc5baffected · git
- a7ceca4398bc835c6ad29d10e1106de4cf0332e1 and later · before 1c42e39b0990371b9d76ae22c3f33eb6df341251affected · git
- a7ceca4398bc835c6ad29d10e1106de4cf0332e1 and later · before 960d1c85381bcaae866dd799b1c905ec5d39ebceaffected · git
- a7ceca4398bc835c6ad29d10e1106de4cf0332e1 and later · before 1db134d0d2a51a136296584854570e5e04adedb0affected · git
- a7ceca4398bc835c6ad29d10e1106de4cf0332e1 and later · before 7cb575b71ab98194d2e040bded3a7281e089c5edaffected · git
- before 5.19not affected · semver
- 6.1.189 and later · up to and including 6.1.*not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.11-1.1 | 7.2.11-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98408Oct 14, 2026 · watchdog: rzv2h: Avoid division by zero0Monitor
- ← EarlierCVE-2026-98409Oct 14, 2026 · watchdog: rtd119x: Avoid division by zero0Monitor
- Later →CVE-2026-98411Oct 14, 2026 · power: sequencing: fix NULL-pointer dereference in pwrseq_device_register()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1c42e39b0990371b9d76ae22c3f33eb6df341251 | Vendor (CNA) |
| Linux Linux | 1db134d0d2a51a136296584854570e5e04adedb0 | Vendor (CNA) |
| Linux Linux | 7cb575b71ab98194d2e040bded3a7281e089c5ed | Vendor (CNA) |
| Linux Linux | 95adc37f47cdf5a5285f7163b24243680af510be | Vendor (CNA) |
| Linux Linux | 960d1c85381bcaae866dd799b1c905ec5d39ebce | Vendor (CNA) |
| Linux Linux | c30b419c7e6fbe31c48a44c828174168b732dc5b | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.11-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 13, 2026+30 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1334 · Oct 15, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/1db134d0d2a51a136296584854570e5e04adedb0
- git.kernel.org/stable/c/7cb575b71ab98194d2e040bded3a7281e089c5ed
- git.kernel.org/stable/c/95adc37f47cdf5a5285f7163b24243680af510be
- git.kernel.org/stable/c/960d1c85381bcaae866dd799b1c905ec5d39ebce
- git.kernel.org/stable/c/c30b419c7e6fbe31c48a44c828174168b732dc5b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.