CVE-2026-63874
Last modified
CVE-2026-63874 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net: mctp: usb: fix race between urb completion and rx_retry cancellation It's possible that sequencing between setting ->stopped and cancelling the rx_retry work (in ndo_stop) could leave us with an urb queued: T1: ndo_stop T2: rx_retry_work ------------ ---------------- LD: ->stopped => false ST: ->stopped <= true usb_kill_urb() mctp_usb_rx_queue() usb_submit_urb() cancel_delayed_work_sync() That urb completion can then re-schedule rx_retry_work. Strenghen the sequencing between the stop (preventing another requeue) and the cancel by updating both atomically under a new rx lock. After setting ->rx_stopped, and cancelling pending work, we know that the requeue cannot occur, so all that's left is killing any pending urb.. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net: mctp: usb: fix race between urb completion and rx_retry cancellation It's possible that sequencing between setting ->stopped and cancelling the rx_retry work (in ndo_stop) could leave us with an urb queued: T1: ndo_stop T2: rx_retry_work ------------ ---------------- LD: ->stopped => false ST: ->stopped <= true usb_kill_urb() mctp_usb_rx_queue() usb_submit_urb() cancel_delayed_work_sync() That urb completion can then re-schedule rx_retry_work. Strenghen the sequencing between the stop (preventing another requeue) and the cancel by updating both atomically under a new rx lock. After setting ->rx_stopped, and cancelling pending work, we know that the requeue cannot occur, so all that's left is killing any pending urb.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 0791c0327a6e4e7691d6fc5ad334c215de04dcc9, < 9c46f3ee1837f6881cb99a52ffecb2760f11dc73; >= 0791c0327a6e4e7691d6fc5ad334c215de04dcc9, < d90feaa3f74bea8dafb6494631a194c70e547d94; >= 0791c0327a6e4e7691d6fc5ad334c215de04dcc9, < 54665dce982689e2fd99b32e9a0dcc204fda8a51 |
| Linux | Linux | 6.15 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-63874?
How severe is CVE-2026-63874?
How do I fix CVE-2026-63874?
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-63868In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63869In the Linux kernel, the following vulnerability has been re…7.6
- CVE-2026-63870In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63871In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63872Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-63873In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63875In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63876In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63877In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63878In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63879In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6388A flaw was found in ArgoCD Image Updater. This vulnerability…9.1
Are you affected by CVE-2026-63874?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
