CVE-2024-56674

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2024-12-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-53322 (ENISA EUVD) · GHSA-4vc6-7qhx-wxq5 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

virtio_net: correct netdev_tx_reset_queue() invocation point

When virtnet_close is followed by virtnet_open, some TX completions can possibly remain unconsumed, until they are finally processed during the first NAPI poll after the netdev_tx_reset_queue(), resulting in a crash [1]. Commit b96ed2c97c79 ("virtio_net: move netdev_tx_reset_queue() call before RX napi enable") was not sufficient to eliminate all BQL crash cases for virtio-net.

This issue can be reproduced with the latest net-next master by running: while :; do ip l set DEV down; ip l set DEV up; done under heavy network TX load from inside the machine.

netdev_tx_reset_queue() can actually be dropped from virtnet_open path; the device is not stopped in any case. For BQL core part, it's just like traffic nearly ceases to exist for some period. For stall detector added to BQL, even if virtnet_close could somehow lead to some TX completions delayed for long, followed by virtnet_open, we can just take it as stall as mentioned in commit 6025b9135f7a ("net: dqs: add NIC stall detector based on BQL"). Note also that users can still reset stall_max via sysfs.

So, drop netdev_tx_reset_queue() from virtnet_enable_queue_pair(). This eliminates the BQL crashes. As a result, netdev_tx_reset_queue() is now explicitly required in freeze/restore path. This patch adds it to immediately after free_unused_bufs(), following the rule of thumb: netdev_tx_reset_queue() should follow any SKB freeing not followed by netdev_tx_completed_queue(). This seems the most consistent and streamlined approach, and now netdev_tx_reset_queue() runs whenever free_unused_bufs() is done.

[1]: ------------[ cut here ]------------ kernel BUG at lib/dynamic_queue_limits.c:99! Oops: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI CPU: 7 UID: 0 PID: 1598 Comm: ip Tainted: G N 6.12.0net-next_main+ #2 Tainted: [N]=TEST Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), \ BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:dql_completed+0x26b/0x290 Code: b7 c2 49 89 e9 44 89 da 89 c6 4c 89 d7 e8 ed 17 47 00 58 65 ff 0d 4d 27 90 7e 0f 85 fd fe ff ff e8 ea 53 8d ff e9 f3 fe ff ff <0f> 0b 01 d2 44 89 d1 29 d1 ba 00 00 00 00 0f 48 ca e9 28 ff ff ff RSP: 0018:ffffc900002b0d08 EFLAGS: 00010297 RAX: 0000000000000000 RBX: ffff888102398c80 RCX: 0000000080190009 RDX: 0000000000000000 RSI: 000000000000006a RDI: 0000000000000000 RBP: ffff888102398c00 R08: 0000000000000000 R09: 0000000000000000 R10: 00000000000000ca R11: 0000000000015681 R12: 0000000000000001 R13: ffffc900002b0d68 R14: ffff88811115e000 R15: ffff8881107aca40 FS: 00007f41ded69500(0000) GS:ffff888667dc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000556ccc2dc1a0 CR3: 0000000104fd8003 CR4: 0000000000772ef0 PKRU: 55555554 Call Trace: ? die+0x32/0x80 ? do_trap+0xd9/0x100 ? dql_completed+0x26b/0x290 ? dql_completed+0x26b/0x290 ? do_error_trap+0x6d/0xb0 ? dql_completed+0x26b/0x290 ? exc_invalid_op+0x4c/0x60 ? dql_completed+0x26b/0x290 ? asm_exc_invalid_op+0x16/0x20 ? dql_completed+0x26b/0x290 __free_old_xmit+0xff/0x170 [virtio_net] free_old_xmit+0x54/0xc0 [virtio_net] virtnet_poll+0xf4/0xe30 [virtio_net] ? __update_load_avg_cfs_rq+0x264/0x2d0 ? update_curr+0x35/0x260 ? reweight_entity+0x1be/0x260 __napi_poll.constprop.0+0x28/0x1c0 net_rx_action+0x329/0x420 ? enqueue_hrtimer+0x35/0x90 ? trace_hardirqs_on+0x1d/0x80 ? kvm_sched_clock_read+0xd/0x20 ? sched_clock+0xc/0x30 ? kvm_sched_clock_read+0xd/0x20 ? sched_clock+0xc/0x30 ? sched_clock_cpu+0xd/0x1a0 handle_softirqs+0x138/0x3e0 do_softirq.part.0+0x89/0xc0 __local_bh_enable_ip+0xa7/0xb0 virtnet_open+0xc8/0x310 [virtio_net] __dev_open+0xfa/0x1b0 __dev_change_flags+0x1de/0x250 dev_change_flags+0x22/0x60 do_setlink.isra.0+0x2df/0x10b0 ? rtnetlink_rcv_msg+0x34f/0x3f0 ? netlink_rcv_skb+0x54/0x100 ? netlink_unicas ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 27, 2024

Last Modified

October 1, 2025

References (2)

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-24ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-24ubuntu
linuxKernel @ 6.12.6 (fixes >=6.11.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.6-1: fixed in 6.12.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.6-1: fixed in 6.12.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 204 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-25 16:55 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-24 03:02 UTCEG score recompute
  13. 2026-10-24 03:02 UTCVendor advisory
  14. 2026-10-24 03:02 UTCGHSA enrichmentGHSA-4vc6-7qhx-wxq5 · GitHub CVSS 5.5
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-18 05:58 UTCEG score recompute
  22. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 70 more
  1. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-12 17:37 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-11 21:03 UTCEG score recompute
  5. 2026-10-11 15:54 UTCEG score recompute
  6. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-10 05:03 UTCOSV refresh
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-02 16:25 UTCEG score recompute
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-09-20 14:44 UTCOSV refresh
  27. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  32. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  33. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  34. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  35. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  36. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  37. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  38. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  39. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  40. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  41. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-09-01 14:54 UTCOSV refresh
  43. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  44. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  47. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  48. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  49. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  50. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  51. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  52. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  53. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  57. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  58. 2026-08-15 16:07 UTCOSV refresh
  59. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  60. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  61. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  62. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  63. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  64. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  65. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  66. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  67. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  68. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  69. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  70. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-56674?
CVE-2024-56674 is a medium-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: virtio_net: correct netdev_tx_reset_queue() invocation point When virtnet_close is followed by virtnet_open, some TX completions can possibly remain unconsumed, until they are finally processed during the first NAPI poll after the…
When was the CVE record for CVE-2024-56674 published?
The CVE record for CVE-2024-56674 was published on December 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 1, 2025; the record at its source may have been updated since.
Is CVE-2024-56674 actively exploited?
CVE-2024-56674 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56674?
CVE-2024-56674 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-56674?
A fix for CVE-2024-56674 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-56674

Explore →

Is Your Infrastructure Affected by CVE-2024-56674?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs