CVE-2025-71114: Linux kernel · Improper Input Validation
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f7b6370d0fbee06a867037d675797a606cb62e57 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in f7b6370d0fbee06a867037d675797a606cb62e57, d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d, c7b986adc9e9336066350542ac5a2005d305ae78 +4
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Jan 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
|
Description
In the Linux kernel, the following vulnerability has been resolved: via_wdt: fix critical boot hang due to unnamed resource allocation The VIA watchdog driver uses allocate_resource() to reserve a MMIO region for the watchdog control register. However, the allocated resource was not given a name, which causes the kernel resource tree to contain an entry marked as "<BAD>" under /proc/iomem on x86 platforms. During boot, this unnamed resource can lead to a critical hang because subsequent resource lookups and conflict checks fail to handle the invalid entry properly.
References
- git.kernel.org/stable/c/1d56025a3af50db0f3da2792f41eb9943eee5324 (opens in a new tab)
- git.kernel.org/stable/c/c7b986adc9e9336066350542ac5a2005d305ae78 (opens in a new tab)
- git.kernel.org/stable/c/47c910965c936724070d2a8094a4c3ed8f452856 (opens in a new tab)
- git.kernel.org/stable/c/d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d (opens in a new tab)
- git.kernel.org/stable/c/f7b6370d0fbee06a867037d675797a606cb62e57 (opens in a new tab)
- git.kernel.org/stable/c/c6a2dd4f2e4e6cbdfe7a1618160281af897b75db (opens in a new tab)
- git.kernel.org/stable/c/7aa31ee9ec92915926e74731378c009c9cc04928 (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-019113.html (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)