PatchSiren cyber security CVE debrief
CVE-2026-98567 Linux CVE debrief
The Linux kernel has a vulnerability where an out-of-range traffic class can cause an out-of-bounds write in the XPS map. This occurs when the number of traffic classes is reduced using netdev_set_num_tc() without properly cleaning up the dev->tc_to_txq[] and dev->prio_tc_map[] arrays. As a result, an attacker can potentially cause a denial-of-service (DoS) by triggering an out-of-bounds write.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-18
- Original CVE updated
- 2026-10-18
- Advisory published
- 2026-10-18
- Advisory updated
- 2026-10-18
Who should care
System administrators and security teams responsible for managing Linux kernel-based systems should be aware of this vulnerability and take steps to mitigate it. They should review and apply the provided kernel patches to fix the vulnerability and ensure that the Linux kernel is updated to a version that includes the fix. Additionally, they should monitor the system for any suspicious activity that may be related to this vulnerability and review compensing
Why it matters
The Linux kernel vulnerability CVE-2026-98567 can cause an out-of-bounds write in the XPS map, potentially leading to a denial-of-service (DoS). System administrators and security teams should review and apply the provided kernel patches to fix the vulnerability.
- Denial-of-service (DoS) due to out-of-bounds write in XPS map
- Potential for system crashes or instability
Technical summary
The vulnerability is caused by the lack of proper cleanup of the dev->tc_to_txq[] and dev->prio_tc_map[] arrays when the number of traffic classes is reduced. This can lead to an out-of-bounds write in the XPS map, potentially causing a denial-of-service (DoS). The bug occurs when netdev_set_num_tc() lowers dev->num_tc without properly cleaning up the arrays, leaving leftover entries that can be accessed by netdev_txq_to_tc() and __netif_set_xps_queue(). To fix this, it's essential to ensure that the number of traffic classes is not reduced without properly cleaning up the arrays.
Defensive priority
Medium
Recommended defensive actions
- Review and apply the provided kernel patches to fix the vulnerability
- Ensure that the Linux kernel is updated to a version that includes the fix
- Monitor the system for any suspicious activity that may be related to this vulnerability
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- 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
Evidence notes
The vulnerability is caused by the lack of proper cleanup of the dev->tc_to_txq[] and dev->prio_tc_map[] arrays when the number of traffic classes is reduced. This can lead to an out-of-bounds write in the XPS map.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-98567 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-98567
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-98567 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-98567
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/1cb8e40525a72c9f1e1cf94c68c172b3b9bbdc81
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/2cc1c3977acbffc417fb5b57699d1df3dcffb5fd
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/4da3b7b8b50f3e2fde54a4c18a82a8e3f6223910
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/6ea8f643053f33622f9116e4e1db58306ece45e3
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/930318290d8509e864c015fe6c9239470b3c579c
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/967e10f40a0c6732db299cbe001df0e859196055
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/9e841723ba482d41ecbf90241c756a16cdfea949
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/eff227a3cb4d0089fbb85c73480bf8abf2e5ae7f
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.