What’s Vulnerable › Vulnerabilities
CVE-2025-71114: via_wdt: fix critical boot hang due to unnamed resource allocation
- Severity: medium (CVSS 5.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-01-14 · updated 2026-10-19
- Weakness: CWE-401
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.
Affected products
- Linux kernel: from 3.3.1 before 5.10.248; from 5.11 before 5.15.198; from 5.16 before 6.1.160; from 6.2 before 6.6.120; from 6.7 before 6.12.64; from 6.13 before 6.18.3 — fixed in 5.10.248, 5.15.198, 6.1.160, 6.12.64, 6.18.3, 6.6.120
How to fix
Upgrade to a fixed version: Linux kernel 5.10.248, 5.15.198, 6.1.160, 6.12.64. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/1d56025a3af50db0f3da2792f41eb9943eee5324
- https://git.kernel.org/stable/c/47c910965c936724070d2a8094a4c3ed8f452856
- https://git.kernel.org/stable/c/7aa31ee9ec92915926e74731378c009c9cc04928
- https://git.kernel.org/stable/c/c6a2dd4f2e4e6cbdfe7a1618160281af897b75db
- https://git.kernel.org/stable/c/c7b986adc9e9336066350542ac5a2005d305ae78
- https://git.kernel.org/stable/c/d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d
- https://git.kernel.org/stable/c/f7b6370d0fbee06a867037d675797a606cb62e57
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
Get alerted when CVE-2025-71114 or the next vulnerability affects your stack