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-2026-90097Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition

Description

In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Skip VMBus module cleanup for non-nested root partition The VMBus module initialization function, hv_acpi_init(), currently does nothing when running in the root partition and root is not nested in another VM. But the initialization function reports success, so the VMBus module is indeed loaded. VMBus functionality is not actually needed, but the VMBus module must be loaded so that hv_vmbus_exists() can answer correctly. Furthermore, the mshv_root dependency on the VMBus module is needed as described in the commit message for 840b740a35bf ("mshv: Add conditional VMBus dependency"). Loading the VMBus module without actually initializing it causes failures if the module should later be unloaded. The module unload code tries to clean up things that were never initialized, resulting in memory faults and a panic. Fix this by having VMBus module exit function perform the same check for non-nested root partition, and do nothing in such a case, just like hv_acpi_init(). In the long run, the code that manages the Hyper-V provided SynIC should be refactored to better coordinate the requirements of root partition scenarios and normal VM scenarios, and to hopefully remove the hv_vmbus_exists() dependnecy between mshv_root and VMBus modules. Preventing the current unload failure scenario is an expediency until such a refactoring is done.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 days 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (13 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 7e279d78664aa91107ebff4b03eca367967f5908 – < 321f650493d6b8169dacd4d5d6f63550dce54d6c
    • affected 7e279d78664aa91107ebff4b03eca367967f5908 – < 4cc1ba2b31065a48fde14e9d53ad399a3ca32e35
    • affected 7e279d78664aa91107ebff4b03eca367967f5908 – < ca1f4a926d08035c52c735a42200e4e5ea548f32
    • affected 7e279d78664aa91107ebff4b03eca367967f5908 – < aa17842bbccaeaba7d05c166019d1c96a41bca54
    • affected 7e279d78664aa91107ebff4b03eca367967f5908 – < 4c19c302cc577bd6b466f6d8e97971777392c2fa
    • affected 7e279d78664aa91107ebff4b03eca367967f5908 – < cee0d90bceae1dee3bcc70f8d6b2ceb5b87deb42
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .