PatchSiren cyber security CVE debrief
CVE-2026-98017 Linux CVE debrief
A vulnerability in the Linux kernel's net/sched has been resolved, where a failed qdisc creation can lead to a use-after-free condition. An RTM_NEWQDISC request can bind a populated shared ingress block during ->init(), publishing an embedded mini_Qdisc to lockless readers. If the same request has an invalid TCA_RATE, estimator setup fails after ->init(); the unwind removes the pointer but synchronously frees its containing qdisc while tc_run() may still hold it.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- HIGH 7.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Linux kernel maintainers, users, and administrators should assess exposure and prioritize verification of affected systems, focusing on potential use-after-free conditions in Linux kernel's net/sched. Affected operators, platforms, vulnerability-management, and security teams should review Linux kernel configurations and versions to determine exposure, verify qdisc creation and estimator setup in use, and consider applying patches or updates from Linux
Why it matters
A vulnerability in the Linux kernel's net/sched has been resolved, where a failed qdisc creation can lead to a use-after-free condition. Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.
- Potential use-after-free condition in Linux kernel's net/sched
- Need to verify qdisc creation and estimator setup in use
- Possible denial of service or privilege escalation
Technical summary
The Linux kernel's net/sched has a vulnerability where a failed qdisc creation can lead to a use-after-free condition. This occurs when an RTM_NEWQDISC request binds a populated shared ingress block during ->init(), publishing an embedded mini_Qdisc to lockless readers. If the same request has an invalid TCA_RATE, estimator setup fails after ->init(); the unwind removes the pointer but synchronously frees its containing qdisc while tc_run() may still hold it.
Defensive priority
Linux kernel maintainers and users should assess exposure and prioritize verification of affected systems.
Recommended defensive actions
- Review Linux kernel configurations and versions to determine exposure
- Verify qdisc creation and estimator setup in use
- Consider applying patches or updates from Linux kernel maintainers
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but the affected versions and exploitation status require verification from the supplied official sources. Linux kernel maintainers and users should verify qdisc creation and estimator setup in use, focusing on potential use-after-free conditions. Defensive verification tasks include reviewing Linux kernel configurations and versions to determine exposure, considering applying patches or updates from Linux kernel maintainers, and tracking exceptions.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-98017 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-98017
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-98017 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-98017
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/156a3bab69744e9225bb9eff8c5cc53da18d5a2e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/20bf6fa34b345333971bd4464a322cce87b83f4e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/5bfe927c5b4b290fad529186218c728589b4b101
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e6662f2100f8d33b0f4d0047c219efd6bba186ea
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.