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-90130vdpa_sim: fix cleanup after worker creation failure

Description

In the Linux kernel, the following vulnerability has been resolved: vdpa_sim: fix cleanup after worker creation failure vdpasim_create() leaves vdpasim->worker as an ERR_PTR when kthread_run_worker() fails. The error path then drops the device reference, which releases the partially initialized simulator. vdpasim_free() unconditionally passes the worker pointer to kthread_destroy_worker(), so the ERR_PTR is dereferenced and can trigger a general protection fault. Store the worker error, clear the pointer, and only clean up the worker when it was successfully initialized. Also make the release path tolerate partially initialized objects by guarding virtqueue and IOTLB cleanup, since the same release path can be reached from other initialization failures. I found this bug myself, though the patch was written with AI assistance.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 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.20% · top 90% of all CVEs (15 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 76acfa7bc54f1e3b9dde396e0a3534493419fd6f – < feafa109f031ed111f7f968e447c13985db498e0
    • affected 76acfa7bc54f1e3b9dde396e0a3534493419fd6f – < 05ddc94afb69e36df59e88cfa9e5c7bf9d10cfd0
    • affected 76acfa7bc54f1e3b9dde396e0a3534493419fd6f – < 68b726b3a01fb02a68843781b17d05ef3d759987
    • affected 76acfa7bc54f1e3b9dde396e0a3534493419fd6f – < ca6f3fa599cb764518df595368b743f856fdb516
    • affected 76acfa7bc54f1e3b9dde396e0a3534493419fd6f – < bd670e5dfd2b01fd9692f61fa1456434c54026a4
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .