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-38151RDMA/cma: Fix hang when cma_netevent_callback fails to queue_work

Description

In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix hang when cma_netevent_callback fails to queue_work The cited commit fixed a crash when cma_netevent_callback was called for a cma_id while work on that id from a previous call had not yet started. The work item was re-initialized in the second call, which corrupted the work item currently in the work queue. However, it left a problem when queue_work fails (because the item is still pending in the work queue from a previous call). In this case, cma_id_put (which is called in the work handler) is therefore not called. This results in a userspace process hang (zombie process). Fix this by calling cma_id_put() if queue_work fails.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 11 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-38151, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.18% · top 92% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 51003b2c872c63d28bcf5fbcc52cf7b05615f7b7 – < 1ac40736c8c4255d8417b937c9715b193f4a87b3
    • affected c2b169fc7a12665d8a675c1ff14bca1b9c63fb9a – < ac7897c0124066b9705ffca252a3662d54fc0c9b
    • affected d23fd7a539ac078df119707110686a5b226ee3bb – < 02e45168e0fd6fdc6f8f7c42c4b500857aa5efb0
    • affected 45f5dcdd049719fb999393b30679605f16ebce14 – < 8b05aa3692e45b8249379dc52b14acc6a104d2e5
    • affected 45f5dcdd049719fb999393b30679605f16ebce14 – < 92a251c3df8ea1991cd9fe00f1ab0cfce18d7711
    • affected b172a4a0de254f1fcce7591833a9a63547c2f447
    • affected 6.1.135 – < 6.1.142
    • affected 6.6.88 – < 6.6.94
    • affected 6.12.25 – < 6.12.34
    • affected 6.14.4 – < 6.15
  • Linux · Linux

    • affected 6.15
    • unaffected < 6.15
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.94 – ≤ 6.6.*
    • unaffected 6.12.34 – ≤ 6.12.*
    • unaffected 6.15.3 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .