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-2025-37949xenbus: Use kref to track req lifetime

Description

In the Linux kernel, the following vulnerability has been resolved: xenbus: Use kref to track req lifetime Marek reported seeing a NULL pointer fault in the xenbus_thread callstack: BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: e030:__wake_up_common+0x4c/0x180 Call Trace: <TASK> __wake_up_common_lock+0x82/0xd0 process_msg+0x18e/0x2f0 xenbus_thread+0x165/0x1c0 process_msg+0x18e is req->cb(req). req->cb is set to xs_wake_up(), a thin wrapper around wake_up(), or xenbus_dev_queue_reply(). It seems like it was xs_wake_up() in this case. It seems like req may have woken up the xs_wait_for_reply(), which kfree()ed the req. When xenbus_thread resumes, it faults on the zero-ed data. Linux Device Drivers 2nd edition states: "Normally, a wake_up call can cause an immediate reschedule to happen, meaning that other processes might run before wake_up returns." ... which would match the behaviour observed. Change to keeping two krefs on each request. One for the caller, and one for xenbus_thread. Each will kref_put() when finished, and the last will free it. This use of kref matches the description in Documentation/core-api/kref.rst

Timeline

  1. ID reserved

    By Linux

  2. · 34 days later

    Published

  3. · 17 months 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

CVSS scores of CVE-2025-37949, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected fd8aa9095a95c02dcc35540a263267c29b8fda9d – < 0e94a246bb6d9538010b6c02d2b1d4717a97b2e5
    • affected fd8aa9095a95c02dcc35540a263267c29b8fda9d – < f1bcac367bc95631afbb918348f30dec887d0e1b
    • affected fd8aa9095a95c02dcc35540a263267c29b8fda9d – < 4d260a5558df4650eb87bc41b2c9ac2d6b2ba447
    • affected fd8aa9095a95c02dcc35540a263267c29b8fda9d – < 8b02f85e84dc6f7c150cef40ddb69af5a25659e5
    • affected fd8aa9095a95c02dcc35540a263267c29b8fda9d – < cbfaf46b88a4c01b64c4186cdccd766c19ae644c
    • affected fd8aa9095a95c02dcc35540a263267c29b8fda9d – < 8e9c8a0393b5f85f1820c565ab8105660f4e8f92
    • affected fd8aa9095a95c02dcc35540a263267c29b8fda9d – < 2466b0f66795c3c426cacc8998499f38031dbb59
    • affected fd8aa9095a95c02dcc35540a263267c29b8fda9d – < 1f0304dfd9d217c2f8b04a9ef4b3258a66eedd27
  • Linux · Linux

    • affected 4.11
    • unaffected < 4.11
    • unaffected 5.4.294 – ≤ 5.4.*
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.183 – ≤ 5.15.*
    • unaffected 6.1.139 – ≤ 6.1.*
    • unaffected 6.6.91 – ≤ 6.6.*
    • unaffected 6.12.29 – ≤ 6.12.*
    • unaffected 6.14.7 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .