[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026011413-CVE-2025-71114-2866@gregkh>
Date: Wed, 14 Jan 2026 16:06:19 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-71114: via_wdt: fix critical boot hang due to unnamed resource allocation
From: Greg Kroah-Hartman <gregkh@...nel.org>
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.
The Linux kernel CVE team has assigned CVE-2025-71114 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.160 with commit 47c910965c936724070d2a8094a4c3ed8f452856
Fixed in 6.6.120 with commit d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d
Fixed in 6.12.64 with commit f7b6370d0fbee06a867037d675797a606cb62e57
Fixed in 6.18.3 with commit c6a2dd4f2e4e6cbdfe7a1618160281af897b75db
Fixed in 6.19-rc1 with commit 7aa31ee9ec92915926e74731378c009c9cc04928
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-71114
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/watchdog/via_wdt.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
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
Powered by blists - more mailing lists