LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can stop some systems from booting when the VIA watchdog driver creates an invalid memory-resource entry. The known impact is availability, not data theft or remote compromise. The source bundle provides kernel stable fixes but no CVSS score or active exploitation evidence.

Executive priority

Track as an availability-risk maintenance item. Prioritize patching for industrial, embedded, or appliance systems where a boot hang could interrupt operations, while avoiding claims of active attack without further evidence.

Technical view

The VIA watchdog driver reserved an MMIO resource with allocate_resource() but did not set a resource name. On x86, that can create a '<BAD>' entry in /proc/iomem. During boot, later resource lookup or conflict handling may mishandle the invalid entry and hang the kernel.

Likely exposure

Exposure appears limited to Linux systems using the VIA watchdog driver path on affected kernel versions or vendor products identified by advisories. Systems without that driver, hardware path, or affected vendor configuration are less likely exposed, but the bundle does not define exact runtime conditions.

Exploitation context

No active exploitation is stated in the source bundle, and KEV is false. The described failure is a boot-time availability condition caused by kernel resource allocation behavior, not a documented remotely exploitable path.

Researcher notes

The record lacks CVSS, CWE, detailed affected configurations, and exploitability analysis. The strongest evidence is the kernel fix description and stable commit references. Validate exposure by kernel branch, driver configuration, hardware context, and vendor advisory coverage.

Mitigation direction

  • Apply Linux vendor kernel updates that include the referenced stable fixes.
  • Review the Siemens advisory if operating Siemens products covered by SSA-019113.
  • If no packaged fix is available, follow vendor guidance for affected kernels.
  • Prioritize systems where boot reliability is operationally critical.

Validation and detection

  • Inventory Linux kernel versions and whether via_wdt is built or loaded.
  • Check vendor advisories for affected product and kernel branch mapping.
  • Confirm deployed kernels contain the relevant stable fix commits.
  • Review boot logs and /proc/iomem for symptoms noted by the advisory.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-71114 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2dunaffected
LinuxLinux3.3, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.