Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-71114, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d – < 1d56025a3af50db0f3da2792f41eb9943eee5324
    • affected dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d – < c7b986adc9e9336066350542ac5a2005d305ae78
    • affected dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d – < 47c910965c936724070d2a8094a4c3ed8f452856
    • affected dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d – < d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d
    • affected dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d – < f7b6370d0fbee06a867037d675797a606cb62e57
    • affected dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d – < c6a2dd4f2e4e6cbdfe7a1618160281af897b75db
    • affected dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d – < 7aa31ee9ec92915926e74731378c009c9cc04928
  • Linux · Linux

    • affected 3.3
    • unaffected < 3.3
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.3 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-71114 badge
[![CVE-2025-71114](https://cveledger.app/badge/CVE-2025-71114.svg)](https://cveledger.app/cve/CVE-2025-71114)

Record last updated .