# CVE-2025-71114: via_wdt: fix critical boot hang due to unnamed resource allocation

> A flaw in the VIA watchdog driver causes a critical boot hang due to improper resource allocation, requiring a kernel patch to resolve.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jan 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2025-71114, DEBIAN-CVE-2025-71114, GHSA-g38x-r7hr-wwff, ROOT-OS-UBUNTU-2204-CVE-2025-71114, ROOT-OS-UBUNTU-2404-CVE-2025-71114, UBUNTU-CVE-2025-71114

## What is CVE-2025-71114?

CVE-2025-71114 is a medium-severity denial of service vulnerability in Linux kernel, published on 14 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-71114?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-71114?

Apply the vendor's patch.

## Is CVE-2025-71114 being exploited?

There is no known exploitation of CVE-2025-71114 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-71114 and fix it if it is affected.

What it is: CVE-2025-71114 is a medium-severity denial of service vulnerability in Linux kernel, published on 14 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-71114 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-71114/ (Markdown: https://insights.sbomify.com/CVE-2025-71114/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-71114
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-71114
- OSV: https://osv.dev/vulnerability/CVE-2025-71114

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-71114/
Summaries are generated and may contain mistakes; the official description above is the record.