# via_wdt: fix critical boot hang due to unnamed resource allocation

CVE record · `CVE-2025-71114`

- **Identifiers:** `CVE-2025-71114`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 14 Jan 2026
- **Updated:** 10 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 14 Jan 2026, 15:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d to before 1d56025a3af50db0f3da2792f41eb9943eee5324` (git)
  - affected: `dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d to before c7b986adc9e9336066350542ac5a2005d305ae78` (git)
  - affected: `dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d to before 47c910965c936724070d2a8094a4c3ed8f452856` (git)
  - affected: `dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d to before d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d` (git)
  - affected: `dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d to before f7b6370d0fbee06a867037d675797a606cb62e57` (git)
  - affected: `dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d to before c6a2dd4f2e4e6cbdfe7a1618160281af897b75db` (git)
  - affected: `dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d to before 7aa31ee9ec92915926e74731378c009c9cc04928` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `3.3`
  - unaffected: `before 3.3` (semver)
  - unaffected: `5.10.248 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.198 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.160 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.120 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.64 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.3 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's via_wdt watchdog driver, from version 3.3 until fixed, allocates an unnamed memory resource that can cause a critical hang during boot on x86 systems. The source gives few details on what conditions trigger it. Upgrade to 5.10.248, 5.15.198, 6.1.160, 6.6.120, or a later stable release in those series.

Written 19 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0018, the 7th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 14 Jan 2026, 15:06 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2025-71114)
- 14 Jan 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-71114)

## Sources

- [CVE List: CVE-2025-71114](https://www.cve.org/CVERecord?id=CVE-2025-71114)
- [NVD: CVE-2025-71114](https://nvd.nist.gov/vuln/detail/CVE-2025-71114)

### References from the CNA

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

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-71114>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-71114/>. Everything for agents: <https://agentprime.io/llms.txt>.
