Linux Kernel up to 6.11.6 qdisc_tree_reduce_backlog iteration

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Linux Kernel up to 6.11.6. Impacted is the function qdisc_tree_reduce_backlog. This manipulation causes iteration. This vulnerability is handled as CVE-2024-53057. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.11.6. Affected by this vulnerability is the function qdisc_tree_reduce_backlog. The manipulation with an unknown input leads to a iteration vulnerability. The CWE definition for the vulnerability is CWE-834. The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed. As an impact it is known to affect availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT In qdisc_tree_reduce_backlog, Qdiscs with major handle ffff: are assumed to be either root or ingress. This assumption is bogus since it's valid to create egress qdiscs with major handle ffff: Budimir Markovic found that for qdiscs like DRR that maintain an active class list, it will cause a UAF with a dangling class pointer. In 066a3b5b2346, the concern was to avoid iterating over the ingress qdisc since its parent is itself. The proper fix is to stop when parent TC_H_ROOT is reached because the only way to retrieve ingress is when a hierarchy which does not contain a ffff: major handle call into qdisc_lookup with TC_H_MAJ(TC_H_ROOT). In the scenario where major ffff: is an egress qdisc in any of the tree levels, the updates will also propagate to TC_H_ROOT, which then the iteration must stop. net/sched/sch_api.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

The weakness was released by Budimir Markovic. The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2024-53057 since 11/19/2024. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 211777 (Debian dsa-5818 : affs-modules-6.1.0-21-4kc-malta-di - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 4.19.323, 5.4.285, 5.10.229, 5.15.171, 6.1.116, 6.6.60 or 6.11.7 eliminates this vulnerability. Applying the patch e7f9a6f97eb0/dbe778b08b51/ce691c814bc7/05df1b1dff8f/580b3189c197/597cf9748c34/9995909615c3/2e95c4384438 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (211777) and CERT Bund (WID-SEC-2024-3509). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • RESF Rocky Linux
  • Dell NetWorker
  • Open Source Linux Kernel
  • Dell Avamar
  • IBM QRadar SIEM
  • IBM DataPower Gateway
  • Dell PowerProtect Data Domain

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Iteration
CWE: CWE-834 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 211777
Nessus Name: Debian dsa-5818 : affs-modules-6.1.0-21-4kc-malta-di - security update

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Kernel 4.19.323/5.4.285/5.10.229/5.15.171/6.1.116/6.6.60/6.11.7
Patch: e7f9a6f97eb0/dbe778b08b51/ce691c814bc7/05df1b1dff8f/580b3189c197/597cf9748c34/9995909615c3/2e95c4384438

Timelineinfo

11/19/2024 🔍
11/19/2024 +0 days 🔍
11/19/2024 +0 days 🔍
12/07/2025 +383 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Researcher: Budimir Markovic
Status: Confirmed

CVE: CVE-2024-53057 (🔍)
GCVE (CVE): GCVE-0-2024-53057
GCVE (VulDB): GCVE-100-285301
CERT Bund: WID-SEC-2024-3509 - Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Entryinfo

Created: 11/19/2024 19:18
Updated: 12/07/2025 17:54
Changes: 11/19/2024 19:18 (59), 11/25/2024 12:15 (2), 07/18/2025 14:24 (7), 12/07/2025 17:54 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!