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-2024-46737nvmet-tcp: fix kernel crash if commands allocation fails

Description

In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: fix kernel crash if commands allocation fails If the commands allocation fails in nvmet_tcp_alloc_cmds() the kernel crashes in nvmet_tcp_release_queue_work() because of a NULL pointer dereference. nvmet: failed to install queue 0 cntlid 1 ret 6 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 Fix the bug by setting queue->nr_cmds to zero in case nvmet_tcp_alloc_cmd() fails.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 23 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-2024-46737, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.76% · top 44% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 03e1fd0327fa5e2174567f5fe9290fe21d21b8f4
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 50632b877ce55356f5d276b9add289b1e7ddc683
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 91dad30c5607e62864f888e735d0965567827bdf
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 7957c731fc2b23312f8935812dee5a0b14b04e2d
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 489f2913a63f528cfe3f21722583fb981967ecda
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 6c04d1e3ab22cc5394ef656429638a5947f87244
    • affected 872d26a391da92ed8f0c0f5cb5fef428067b7f30 – < 5572a55a6f830ee3f3a994b6b962a5c327d28cb3
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.4.284 – ≤ 5.4.*
    • unaffected 5.10.226 – ≤ 5.10.*
    • unaffected 5.15.167 – ≤ 5.15.*
    • unaffected 6.1.110 – ≤ 6.1.*
    • unaffected 6.6.51 – ≤ 6.6.*
    • unaffected 6.10.10 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .