CVE-2024-56770

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 2025-01-08. 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-53413 (ENISA EUVD) · GHSA-m7p9-xw5x-w2c4 (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.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net/sched: netem: account for backlog updates from child qdisc

In general, 'qlen' of any classful qdisc should keep track of the number of packets that the qdisc itself and all of its children holds. In case of netem, 'qlen' only accounts for the packets in its internal tfifo. When netem is used with a child qdisc, the child qdisc can use 'qdisc_tree_reduce_backlog' to inform its parent, netem, about created or dropped SKBs. This function updates 'qlen' and the backlog statistics of netem, but netem does not account for changes made by a child qdisc. 'qlen' then indicates the wrong number of packets in the tfifo. If a child qdisc creates new SKBs during enqueue and informs its parent about this, netem's 'qlen' value is increased. When netem dequeues the newly created SKBs from the child, the 'qlen' in netem is not updated. If 'qlen' reaches the configured sch->limit, the enqueue function stops working, even though the tfifo is not full.

Reproduce the bug: Ensure that the sender machine has GSO enabled. Configure netem as root qdisc and tbf as its child on the outgoing interface of the machine as follows: $ tc qdisc add dev root handle 1: netem delay 100ms limit 100 $ tc qdisc add dev parent 1:0 tbf rate 50Mbit burst 1542 latency 50ms

Send bulk TCP traffic out via this interface, e.g., by running an iPerf3 client on the machine. Check the qdisc statistics: $ tc -s qdisc show dev

Statistics after 10s of iPerf3 TCP test before the fix (note that netem's backlog > limit, netem stopped accepting packets): qdisc netem 1: root refcnt 2 limit 1000 delay 100ms Sent 2767766 bytes 1848 pkt (dropped 652, overlimits 0 requeues 0) backlog 4294528236b 1155p requeues 0 qdisc tbf 10: parent 1:1 rate 50Mbit burst 1537b lat 50ms Sent 2767766 bytes 1848 pkt (dropped 327, overlimits 7601 requeues 0) backlog 0b 0p requeues 0

Statistics after the fix: qdisc netem 1: root refcnt 2 limit 1000 delay 100ms Sent 37766372 bytes 24974 pkt (dropped 9, overlimits 0 requeues 0) backlog 0b 0p requeues 0 qdisc tbf 10: parent 1:1 rate 50Mbit burst 1537b lat 50ms Sent 37766372 bytes 24974 pkt (dropped 327, overlimits 96017 requeues 0) backlog 0b 0p requeues 0

tbf segments the GSO SKBs (tbf_segment) and updates the netem's 'qlen'. The interface fully stops transferring packets and "locks". In this case, the child qdisc and tfifo are empty, but 'qlen' indicates the tfifo is at its limit and no more packets are accepted.

This patch adds a counter for the entries in the tfifo. Netem's 'qlen' is only decreased when a packet is returned by its dequeue function, and not during enqueuing into the child qdisc. External updates to 'qlen' are thus accounted for and only the behavior of the backlog statistics changes. As in other qdiscs, 'qlen' then keeps track of how many packets are held in netem and all of its children. As before, sch->limit remains as the maximum number of packets in the tfifo. The same applies to netem's backlog statistics.

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.3% × 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.3%
EPSS %ILE
19th
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.3% within 30 daysSource: FIRST EPSS. 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

January 8, 2025

Last Modified

October 15, 2026

Advisory Details (10)

Auto-updated Oct 15, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4075-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Web page

net/sched: netem: account for backlog updates from child qdisc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8d4bc455047cf3903cd6f85f49978987dbb3027
Web page

net/sched: netem: account for backlog updates from child qdisc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c2047b0e216c8edce227d7c42f99ac2877dad0e4
Web page

net/sched: netem: account for backlog updates from child qdisc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83c6ab12f08dcc09d4c5ac86fdb89736b28f1d31
Web page

net/sched: netem: account for backlog updates from child qdisc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3824c5fad18eeb7abe0c4fc966f29959552dca3e
Web page

net/sched: netem: account for backlog updates from child qdisc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/356078a5c55ec8d2061fcc009fb8599f5b0527f9
Web page

net/sched: netem: account for backlog updates from child qdisc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/216509dda290f6db92c816dd54b83c1df9da9e76
Web page

net/sched: netem: account for backlog updates from child qdisc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10df49cfca73dfbbdb6c4150d859f7e8926ae427

Vendor Advisories for CVE-2024-56770(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-edge (5.15.0.1077.83~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-10-15ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1060 (5.4.0-1060.64) @ focal2026-10-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-10-15ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1086.95~20.04.1.61) @ focal2026-10-15ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1077.83~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-virtual-hwe-16.04-edge (4.15.0.237.249~16.04.1) @ xenial2026-10-15ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.268.274) @ xenial2026-10-15ubuntu
ubuntulinux-tools-azure (4.15.0.1188.203~14.04.1) @ trusty2026-10-15ubuntu
ubuntulinux-tools-fips (4.4.0.1113.114) @ xenial2026-10-15ubuntu
ubuntulinux-tools-gcp-fips (4.15.0.2081.79) @ bionic2026-10-15ubuntu
ubuntulinux-tools-azure-edge (4.15.0.1188.203~16.04.1) @ xenial2026-10-15ubuntu
ubuntulinux-tools-azure-fips (4.15.0.2097.93) @ bionic2026-10-15ubuntu
ubuntulinux-tools-aws (4.4.0.1143.140) @ trusty2026-10-15ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.268.302~14.04.1) @ trusty2026-10-15ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1028.31~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-60.63.1~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-realtime (6.8.1-1022.23) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-60.63~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1028.28) @ noble2026-10-15ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-10-15ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-10-15ubuntu
linuxKernel @ 5.4.288 (fixes >=3.3.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)
  • every version up to 6.1.123-1: fixed in 6.1.123-1
—
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
—

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 40× 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 202 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 107 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-56770?
CVE-2024-56770 is a medium-severity vulnerability; its CVE record was published on January 8, 2025. In the Linux kernel, the following vulnerability has been resolved: net/sched: netem: account for backlog updates from child qdisc In general, 'qlen' of any classful qdisc should keep track of the number of packets that the qdisc itself and all of its children holds. In case of netem, 'qlen' only…
When was the CVE record for CVE-2024-56770 published?
The CVE record for CVE-2024-56770 was published on January 8, 2025. 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 15, 2026; the record at its source may have been updated since.
Is CVE-2024-56770 actively exploited?
CVE-2024-56770 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56770?
CVE-2024-56770 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-56770?
A fix for CVE-2024-56770 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56770 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-56770?

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