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 <oif> root handle 1: netem delay 100ms limit 100 $ tc qdisc add dev <oif> 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 <oif> 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.
This page covers CVE-2024-56770 as tracked by Ubuntu, for the package linux. The fix is available in version 6.8.0-60.63; earlier versions remain affected.
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
UBUNTU-CVE-2024-56770 is recorded against 135 packages.
Published on 8 January 2025 and last revised on 18 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
ubuntu.com (Report)
www.cve.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
linux has other advisories on record. If you are patching this one, these are worth checking on the same host:
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux | — | 6.8.0-60.63 |
| linux-allwinner-5.19 | — | — |
| linux-aws | — | 6.8.0-1029.31 |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.15 | — | 5.15.0-1080.87~20.04.1 |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.4 | — | 5.4.0-1142.152~18.04.1 |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-aws-6.8 | — | 6.8.0-1029.31~22.04.1 |
| linux-aws-fips | — | 5.15.0-1080.87+fips1 |
| linux-aws-hwe | — | 4.15.0-1180.193~16.04.1 |
| linux-azure | — | 6.8.0-1029.34 |
| linux-azure-4.15 | — | 4.15.0-1188.203 |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.15 | — | 5.15.0-1086.95~20.04.1 |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.4 | — | 5.4.0-1147.154~18.04.1 |
| linux-azure-5.8 | — | — |
| linux-azure-6.11 | — | 6.11.0-1012.12~24.04.1 |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-6.8 | — | 6.8.0-1029.34~22.04.1 |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-azure-fips | — | 5.15.0-1083.92+fips1 |
| linux-azure-nvidia | — | 6.8.0-1016.17 |
| linux-bluefield | — | — |
| linux-fips | — | 6.8.0-78.78+fips1 |
| linux-gcp | — | 6.8.0-1030.32 |
| linux-gcp-4.15 | — | 4.15.0-1173.190 |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.15 | — | 5.15.0-1081.90~20.04.1 |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.4 | — | 5.4.0-1145.154~18.04.1 |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.11 | — | 6.11.0-1011.11~24.04.1 |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gcp-6.8 | — | 6.8.0-1030.32~22.04.1 |
| linux-gcp-fips | — | 5.15.0-1079.88+fips1 |
| linux-gke | — | 6.8.0-1025.29 |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop | — | 6.8.0-1012.14 |
| linux-gkeop-5.15 | — | — |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.15 | — | 5.15.0-136.147~20.04.1 |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.4 | — | 5.4.0-211.231~18.04.1 |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.11 | — | 6.11.0-21.21~24.04.1 |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-6.8 | — | 6.8.0-60.63~22.04.1 |
| linux-hwe-edge | — | — |
| linux-ibm | — | 6.8.0-1026.26 |
| linux-ibm-5.15 | — | 5.15.0-1074.77~20.04.1 |
| linux-ibm-5.4 | — | 5.4.0-1090.95~18.04.1 |
| linux-ibm-6.8 | — | 6.8.0-1026.26~22.04.1 |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | 5.15.0-1073.75 |
| linux-intel-iotg | — | 5.15.0-1075.81 |
| linux-intel-iotg-5.15 | — | 5.15.0-1077.83~20.04.1 |
| linux-iot | — | 5.4.0-1048.51 |
| linux-kvm | — | 5.15.0-1076.81 |
| linux-lowlatency | — | 6.8.0-60.63.1 |
| linux-lowlatency-hwe-5.15 | — | 5.15.0-135.146~20.04.1 |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | — |
| linux-lowlatency-hwe-6.8 | — | 6.8.0-60.63.1~22.04.1 |
| linux-lts-xenial | — | 4.4.0-268.302~14.04.1 |
| linux-nvidia | — | 6.8.0-1028.31 |
| linux-nvidia-6.11 | — | 6.11.0-1007.7 |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-nvidia-6.8 | — | 6.8.0-1028.31~22.04.1 |
| linux-nvidia-lowlatency | — | 6.8.0-1028.31.1 |
| linux-nvidia-tegra | — | 6.8.0-1008.8 |
| linux-nvidia-tegra-5.15 | — | 5.15.0-1039.39~20.04.1 |
| linux-nvidia-tegra-igx | — | 5.15.0-1021.21 |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.11 | — | 6.11.0-1017.17 |
| linux-oem-6.5 | — | — |
| linux-oem-6.8 | — | 6.8.0-1028.28 |
| linux-oracle | — | 6.8.0-1026.27 |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.15 | — | 5.15.0-1077.83~20.04.1 |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.4 | — | 5.4.0-1140.149~18.04.1 |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-oracle-6.8 | — | 6.8.0-1026.27~22.04.1 |
| linux-raspi | — | 6.8.0-1028.32 |
| linux-raspi-5.4 | — | 5.4.0-1129.142~18.04.1 |
| linux-raspi-realtime | — | 6.8.0-2023.24 |
| linux-raspi2 | — | — |
| linux-realtime | — | 6.8.1-1022.23 |
| linux-realtime-6.8 | — | 6.8.1-1022.23~22.04.1 |
| linux-riscv | — | 6.8.0-60.63.1 |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.15 | — | 5.15.0-1075.79~20.04.1 |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-riscv-6.8 | — | 6.8.0-62.65~22.04.1 |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
| linux-xilinx | — | 6.8.0-1017.18 |
| linux-xilinx-zynqmp | — | 5.15.0-1044.48 |
References
Similar Threats
Vulnerability Monitoring
UBUNTU-CVE-2024-56770 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
Stay up to date with the latest from Boteraser.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
These cookies are needed for adding comments on this website.
These cookies are used for managing login functionality on this website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
You can find more information in our Cookie Policy and Privacy Policy.