Bug 2429579 (CVE-2025-71114)

Summary: CVE-2025-71114 kernel: via_wdt: fix critical boot hang due to unnamed resource allocation
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedKeywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A boot hang vulnerability was found in the Linux kernel's VIA watchdog timer driver. When allocating a MMIO resource for the watchdog control register, the driver fails to assign a name to the resource. This creates an invalid "<BAD>" entry in the kernel resource tree under /proc/iomem, which can cause subsequent resource lookups and conflict checks to fail, leading to a system hang during boot.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-01-14 16:01:50 UTC 
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.
Comment 1 Jon Moroney 2026-01-14 20:55:34 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026011413-CVE-2025-71114-2866@gregkh/T