CVE-2026-64207
Last modified
CVE-2026-64207 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net/sched: dualpi2: fix GSO backlog accounting When DualPI2 splits a GSO skb into N segments, it propagates N additional packets to its parent before returning NET_XMIT_SUCCESS. The parent then accounts for the original skb once more, leaving its qlen one larger than the number of packets actually queued. With QFQ as the parent, after all real packets are dequeued, QFQ still has a non-zero qlen while its in-service aggregate has no active classes. qfq_choose_next_agg() returns NULL and qfq_dequeue() passes the result to qfq_peek_skb(), causing a NULL pointer dereference. Follow the same pattern used by tbf_segment() and taprio: count only successfully queued segments, propagate the difference between the original skb and those segments, and return NET_XMIT_SUCCESS whenever at least one segment was queued.. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: dualpi2: fix GSO backlog accounting When DualPI2 splits a GSO skb into N segments, it propagates N additional packets to its parent before returning NET_XMIT_SUCCESS. The parent then accounts for the original skb once more, leaving its qlen one larger than the number of packets actually queued. With QFQ as the parent, after all real packets are dequeued, QFQ still has a non-zero qlen while its in-service aggregate has no active classes. qfq_choose_next_agg() returns NULL and qfq_dequeue() passes the result to qfq_peek_skb(), causing a NULL pointer dereference. Follow the same pattern used by tbf_segment() and taprio: count only successfully queued segments, propagate the difference between the original skb and those segments, and return NET_XMIT_SUCCESS whenever at least one segment was queued.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.17, < 6.18.39 |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64207?
How severe is CVE-2026-64207?
How do I fix CVE-2026-64207?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64192In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64193Net::DNS versions through 1.55 for Perl allow remote executi…9.8
- CVE-2026-64194Net::DNS versions through 1.55 for Perl allow Denial of Serv…7.5
- CVE-2026-6420A flaw was found in Keylime. An attacker with root access on…6.3
- CVE-2026-64205In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64206In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64208In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64209In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-6421A vulnerability has been found in Mobatek MobaXterm Home Edi…7
- CVE-2026-64210In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64211In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64212In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64207?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
