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-98079btrfs: zstd: fix lost wakeup when waiting for a workspace

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: zstd: fix lost wakeup when waiting for a workspace A writer can sleep forever in zstd_get_workspace() even though a workspace is free. When zstd_alloc_workspace() fails, the task is queued on zwsm->wait and schedules unconditionally, never re-testing the pool. zstd_put_workspace() publishes the workspace and then calls cond_wake_up(), which only wakes when a sleeper is already visible, so a workspace returned between the failed allocation and prepare_to_wait() wakes nobody. The window is wide: zstd_alloc_workspace() goes through kvmalloc() and may enter reclaim. Only a max level workspace triggers the wakeup and one is deliberately kept allocated as the fallback every waiter waits for, so once its wakeup is lost the writer stays in TASK_UNINTERRUPTIBLE until some other task happens to return one. Re-check the pool after prepare_to_wait() has published the waiter, and use the workspace if one turned up.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 26 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: Undergoing Analysis.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (12 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 3f93aef535c8ea03e40cd8acf0753b3e6ed33e96 – < 14d982762945d9945c60bbd48b77df194dd8e28d
    • affected 3f93aef535c8ea03e40cd8acf0753b3e6ed33e96 – < 844603cf842ee67640d33f350e3fa60f3de7fad3
    • affected 3f93aef535c8ea03e40cd8acf0753b3e6ed33e96 – < d8f57049521948df5f50797141472fbbed3b0723
    • affected 3f93aef535c8ea03e40cd8acf0753b3e6ed33e96 – < 0de9f31d447ae71ab08c7850a321682f8d2907c3
    • affected 3f93aef535c8ea03e40cd8acf0753b3e6ed33e96 – < 2acb9f3d1cc8f65dc81ed55e238cbf8e5b60bff7
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 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-98079 badge
[![CVE-2026-98079](https://cveledger.app/badge/CVE-2026-98079.svg)](https://cveledger.app/cve/CVE-2026-98079)

Record last updated .