CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag
In the Linux kernel, the following vulnerability has been resolved:
net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag
This is more of a preventive patch to make the code more consistent and
to prevent possible exploits that employ child qlen manipulations on qfq.
use cl_is_active instead of relying on the child qdisc's qlen to determine
class activation.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23105 is a Linux kernel flaw in the QFQ traffic scheduler. A local low-privileged user could potentially influence scheduler state in a way the kernel maintainers considered exploitable. The CVSS score is high, but the provided sources do not show active exploitation.
Executive priority
Treat as a high-priority kernel maintenance item, especially on systems with untrusted local users. There is no sourced evidence of active exploitation, so prioritize alongside normal high-severity Linux kernel patch cycles rather than emergency incident response.
Technical view
The QFQ scheduler’s qfq_rm_from_ag logic relied on a child qdisc qlen value to decide whether a class was active. The fix uses cl_is_active instead, making class activation state consistent and reducing risk from child qlen manipulation. CVSS indicates local access, low complexity, low privileges, no user interaction, and high CIA impact.
Likely exposure
Exposure is most relevant for Linux systems running affected kernel versions or branches with QFQ available. The provided record lists Linux kernel versions including 3.8 and several stable branch versions as affected, but it does not map distributions or packaged kernel names.
Exploitation context
The source says this was a preventive patch to prevent possible exploits using child qlen manipulation. KEV is false, and no cited source in the bundle confirms public exploitation or active attacks.
Researcher notes
The public record is sparse: no CWE, no exploit details, and no distro mapping are provided. Analysis should focus on the upstream scheduler change and affected branch coverage. Avoid assuming reachability beyond local, low-privilege access as stated by CVSS.
Mitigation direction
Apply Linux stable or distribution kernel updates containing the referenced fixes.
Check your Linux vendor advisory for exact package names and fixed builds.
Prioritize multi-user servers, developer workstations, and shared hosting systems.
Reduce unnecessary local user access where timely patching is blocked.
Track the listed kernel stable commits against internally maintained kernels.
Validation and detection
Inventory kernel versions across Linux assets.
Confirm whether deployed kernels include one of the referenced stable fixes.
Check whether QFQ support is enabled or available in relevant kernels.
Review distro advisories for CVE-2026-23105 package status.
Verify patched kernels are booted, not merely installed.
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-2026-23105 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
0ADP providers
8Source 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.