CVE-2026-98121: Linux kernel · watchdog: msc313e: Fix NULL pointer dereference in PM callbacks
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e3eceb76515910746e6268c4e4ac1c07516ebd7b : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e3eceb76515910746e6268c4e4ac1c07516ebd7b, b02f902fe4b59d65f74a25c4523a75453bd3f808, afc3ea51e479289a23c642cc8bade67b94225ed9 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel source code as indicated by the listed fixed commit versions. Users and administrators should update to a kernel version that includes these fixes to remediate the vulnerability.
Description
A NULL pointer dereference vulnerability was identified and fixed in the Linux kernel watchdog driver for the msc313e platform. The issue occurs because the driver data for the platform device was not set during probe, causing subsequent power management callbacks to dereference a NULL pointer. This flaw was addressed by properly setting the platform device driver data in the probe function.
References
- git.kernel.org/stable/c/960251cc4a413d8f1eef2a2c6aca41073b57ce16 (opens in a new tab)
- git.kernel.org/stable/c/afc3ea51e479289a23c642cc8bade67b94225ed9 (opens in a new tab)
- git.kernel.org/stable/c/a135415be56839e555e0bcdd5ffb8d2f5f947bd7 (opens in a new tab)
- git.kernel.org/stable/c/b02f902fe4b59d65f74a25c4523a75453bd3f808 (opens in a new tab)
- git.kernel.org/stable/c/744b25040d8206f7925b8ba0be5edf93fa4bf81e (opens in a new tab)
- git.kernel.org/stable/c/6495dc16e635356fd2b7535dcbf9b6779de4e753 (opens in a new tab)
- git.kernel.org/stable/c/e3eceb76515910746e6268c4e4ac1c07516ebd7b (opens in a new tab)