Skip to main content
VulnerabilityPublished Updated

CVE-2025-71114: Linux kernel · Improper Input Validation

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f7b6370d0fbee06a867037d675797a606cb62e57 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in f7b6370d0fbee06a867037d675797a606cb62e57, d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d, c7b986adc9e9336066350542ac5a2005d305ae78 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, < f7b6370d0fbee06a867037d675797a606cb62e57
Fixed in
  • f7b6370d0fbee06a867037d675797a606cb62e57
LinuxLinuxAffected
  • ≥ dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, < d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d
Fixed in
  • d2c7c90aca7b37f60f16b2bedcfeb16204f2f35d
LinuxLinuxAffected
  • ≥ dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, < c7b986adc9e9336066350542ac5a2005d305ae78
Fixed in
  • c7b986adc9e9336066350542ac5a2005d305ae78
LinuxLinuxAffected
  • ≥ dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, < c6a2dd4f2e4e6cbdfe7a1618160281af897b75db
Fixed in
  • c6a2dd4f2e4e6cbdfe7a1618160281af897b75db
LinuxLinuxAffected
  • ≥ dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, < 47c910965c936724070d2a8094a4c3ed8f452856
Fixed in
  • 47c910965c936724070d2a8094a4c3ed8f452856
LinuxLinuxAffected
  • ≥ dc3c56b703dad4aec8a9b3dd86f03a90d0c26a2d, < 7aa31ee9ec92915926e74731378c009c9cc04928
Fixed in
  • 7aa31ee9ec92915926e74731378c009c9cc04928

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.

References

Community reviews

Loading reviews…