LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21971: net_sched: Prevent creation of classes with TC_H_ROOT

In the Linux kernel, the following vulnerability has been resolved: net_sched: Prevent creation of classes with TC_H_ROOT The function qdisc_tree_reduce_backlog() uses TC_H_ROOT as a termination condition when traversing up the qdisc tree to update parent backlog counters. However, if a class is created with classid TC_H_ROOT, the traversal terminates prematurely at this class instead of reaching the actual root qdisc, causing parent statistics to be incorrectly maintained. In case of DRR, this could lead to a crash as reported by Mingi Cho. Prevent the creation of any Qdisc class with classid TC_H_ROOT (0xFFFFFFFF) across all qdisc types, as suggested by Jamal.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw affects traffic-control queue configuration. A class can use an identifier reserved to mean “root,” causing the kernel to stop updating parent queue statistics too early. Accounting becomes inconsistent, and the DRR scheduler may crash the system. Evidence describes a local condition and crash, not confirmed remote compromise or active exploitation.

Executive priority

Treat this as accelerated high-severity kernel maintenance, prioritizing shared systems where untrusted local principals can alter traffic control. The supplied evidence does not support remote exploitation or an active campaign, so emergency incident response is not justified solely by this bundle. Kernel crash potential still warrants timely remediation.

Technical view

qdisc_tree_reduce_backlog() walks parent qdiscs until TC_H_ROOT. Permitting a qdisc class to use that same class ID makes traversal terminate before reaching the actual root, leaving backlog statistics incorrectly maintained. In DRR, the resulting inconsistency can cause a crash. Stable fixes prevent TC_H_ROOT class creation across all qdisc types.

Likely exposure

Potentially exposed systems run a kernel covered by the listed affected entries and allow a local principal to create traffic-control classes. Risk is most direct where DRR is used. Because the supplied version representation mixes releases and branch endpoints, confirm exact package exposure against vendor advisories or the corresponding stable fix commit.

Exploitation context

The bundle marks KEV false and provides no evidence of active exploitation or public weaponization. It documents a reported DRR crash. The CVSS vector models a local, low-privilege attack path, but the supplied evidence does not detail the exact permissions or configuration required.

Researcher notes

TC_H_ROOT is both the parent-walk termination sentinel and, before the fix, an accepted class ID. That collision prematurely stops backlog propagation. The resolution rejects this class ID globally. No CWE is supplied, and the sources do not demonstrate confidentiality or integrity exploitation despite the CVSS impact values.

Mitigation direction

  • Apply vendor-supported kernel updates containing the relevant stable fix, following distribution guidance.
  • Reboot or otherwise activate the updated kernel as directed, then confirm the running build.
  • Until patched, restrict untrusted local access and permission to configure traffic-control classes.
  • Review applicable vendor advisories for branch-specific package status and backport coverage.

Validation and detection

  • Inventory active kernel versions and distribution package revisions across potentially affected systems.
  • Map each build to its vendor advisory and corresponding stable fix commit.
  • Confirm the active patched kernel rejects classes using the reserved TC_H_ROOT identifier.
  • Review which local users or workloads can create or modify traffic-control classes.
  • Examine kernel logs and crash records for DRR or qdisc-related failures.
Prepared
Confidence
medium
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-21971 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
11Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-21971Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux066a3b5b2346febf9a655b444567b7138e3bb939, 066a3b5b2346febf9a655b444567b7138e3bb939, 066a3b5b2346febf9a655b444567b7138e3bb939, 066a3b5b2346febf9a655b444567b7138e3bb939, 066a3b5b2346febf9a655b444567b7138e3bb939, 066a3b5b2346febf9a655b444567b7138e3bb939, 066a3b5b2346febf9a655b444567b7138e3bb939, 066a3b5b2346febf9a655b444567b7138e3bb939unaffected
LinuxLinux2.6.25, 0, 5.4.292, 5.10.236, 5.15.180, 6.1.132, 6.6.84, 6.12.20, 6.13.8, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.