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-90140cuse: wait for pending RCU callbacks on module exit

Description

In the Linux kernel, the following vulnerability has been resolved: cuse: wait for pending RCU callbacks on module exit Since commit 053fc4f755ad ("fuse: fix UAF in rcu pathwalks"), fuse_conn_put() frees the fuse_conn through call_rcu() rather than synchronously. For cuse, fc->release is cuse_fc_release(), which lives in the cuse module. If the module is removed before the RCU grace period ends, the callback jumps into freed module memory: userspace / module unload | RCU softirq ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ close(/dev/cuse) | cuse_channel_release() | fuse_dev_release() | fuse_conn_put(fch->conn) | call_rcu(delayed_release) ------+---> callback queued | rmmod cuse | cuse_exit() | cuse_channel_destroy() | ... | return | | <module text freed> | | rcu_do_batch() | delayed_release() | fc->release() | -> cuse_fc_release() | ^^^ freed text! The freed module text is unmapped by vfree(), so the jump into the stale callback triggers a page-fault Oops. If the virtual address is subsequently reused, the callback could execute unrelated code (undefined behaviour). Fix this by calling rcu_barrier() in cuse_exit() so that any pending fuse_conn release callback completes before the module is removed.

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.21% · top 89% of all CVEs (19 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 bfbab62ca69f72bcd14ea30de1fb98f6080ad464 – < 7fe415e1cd8fa875be263670c0ab47109818abb6
    • affected a8f650b93e55764ca9ff8e1ddebc151f57024086 – < 45ae914b2f6ea56fc2f1c017fdee4e995bcb4c0e
    • affected 535e9bd0e8f8d8cfdc29de7cdb902b5041427fe6 – < ac5c499413385cea3e0220d6050408d50842891d
    • affected 053fc4f755ad43cf35210677bcba798ccdc48d0c – < a1b46aee33d83f14ed62d7fdef1a91d3e0b732a9
    • affected 053fc4f755ad43cf35210677bcba798ccdc48d0c – < 389bd349ddbcf90dbd8a4f2a4ab6e552d53df134
    • affected 053fc4f755ad43cf35210677bcba798ccdc48d0c – < c40f3f24839f8404325a2099e26c2a04786ae309
    • affected 053fc4f755ad43cf35210677bcba798ccdc48d0c – < 4deb3edead0c0e172cc7349e8855d741d3c5e162
    • affected 5.15.166 – < 5.15.221
    • affected 6.1.107 – < 6.1.188
    • affected 6.6.48 – < 6.6.157
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • 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

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .