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-55916Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet

Description

In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: util: Avoid accessing a ringbuffer not initialized yet If the KVP (or VSS) daemon starts before the VMBus channel's ringbuffer is fully initialized, we can hit the panic below: hv_utils: Registering HyperV Utility Driver hv_vmbus: registering driver hv_utils ... BUG: kernel NULL pointer dereference, address: 0000000000000000 CPU: 44 UID: 0 PID: 2552 Comm: hv_kvp_daemon Tainted: G E 6.11.0-rc3+ #1 RIP: 0010:hv_pkt_iter_first+0x12/0xd0 Call Trace: ... vmbus_recvpacket hv_kvp_onchannelcallback vmbus_on_event tasklet_action_common tasklet_action handle_softirqs irq_exit_rcu sysvec_hyperv_stimer0 </IRQ> <TASK> asm_sysvec_hyperv_stimer0 ... kvp_register_done hvt_op_read vfs_read ksys_read __x64_sys_read This can happen because the KVP/VSS channel callback can be invoked even before the channel is fully opened: 1) as soon as hv_kvp_init() -> hvutil_transport_init() creates /dev/vmbus/hv_kvp, the kvp daemon can open the device file immediately and register itself to the driver by writing a message KVP_OP_REGISTER1 to the file (which is handled by kvp_on_msg() ->kvp_handle_handshake()) and reading the file for the driver's response, which is handled by hvt_op_read(), which calls hvt->on_read(), i.e. kvp_register_done(). 2) the problem with kvp_register_done() is that it can cause the channel callback to be called even before the channel is fully opened, and when the channel callback is starting to run, util_probe()-> vmbus_open() may have not initialized the ringbuffer yet, so the callback can hit the panic of NULL pointer dereference. To reproduce the panic consistently, we can add a "ssleep(10)" for KVP in __vmbus_open(), just before the first hv_ringbuffer_init(), and then we unload and reload the driver hv_utils, and run the daemon manually within the 10 seconds. Fix the panic by reordering the steps in util_probe() so the char dev entry used by the KVP or VSS daemon is not created until after vmbus_open() has completed. This reordering prevents the race condition from happening.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 16 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-55916, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/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.22% · top 87% of all CVEs (17 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e0fa3e5e7df61eb2c339c9f0067c202c0cdeec2c – < f091a224a2c82f1e302b1768d73bb6332f687321
    • affected e0fa3e5e7df61eb2c339c9f0067c202c0cdeec2c – < d81f4e73aff9b861671df60e5100ad25cc16fbf8
    • affected e0fa3e5e7df61eb2c339c9f0067c202c0cdeec2c – < 042253c57be901bfd19f15b68267442b70f510d5
    • affected e0fa3e5e7df61eb2c339c9f0067c202c0cdeec2c – < 718fe694a334be9d1a89eed22602369ac18d6583
    • affected e0fa3e5e7df61eb2c339c9f0067c202c0cdeec2c – < 89fcec5e466b3ac9b376e0d621c71effa1a7983f
    • affected e0fa3e5e7df61eb2c339c9f0067c202c0cdeec2c – < 3dd7a30c6d7f90afcf19e9b072f572ba524d7ec6
    • affected e0fa3e5e7df61eb2c339c9f0067c202c0cdeec2c – < 07a756a49f4b4290b49ea46e089cbe6f79ff8d26
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.4.289 – ≤ 5.4.*
    • unaffected 5.10.233 – ≤ 5.10.*
    • unaffected 5.15.176 – ≤ 5.15.*
    • unaffected 6.1.122 – ≤ 6.1.*
    • unaffected 6.6.68 – ≤ 6.6.*
    • unaffected 6.12.7 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .