0.0
NA
CVE-2026-63874
net: mctp: usb: fix race between urb completion and rx_retry cancellation
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.

INFO

Published Date :

July 19, 2026, 3:16 p.m.

Last Modified :

July 19, 2026, 3:16 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-63874 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Apply kernel updates to address a race condition in the mctp USB driver.
  • Update the Linux kernel to the latest stable version.
  • Apply the specific patch addressing the race condition.
  • Recompile and install the kernel if necessary.
  • Restart the system to load the updated kernel.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-63874.

URL Resource
https://git.kernel.org/stable/c/54665dce982689e2fd99b32e9a0dcc204fda8a51
https://git.kernel.org/stable/c/9c46f3ee1837f6881cb99a52ffecb2760f11dc73
https://git.kernel.org/stable/c/d90feaa3f74bea8dafb6494631a194c70e547d94
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-63874 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-63874 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-63874 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-63874 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 19, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '0791c0327a6e4e7691d6fc5ad334c215de04dcc9', 'lessThan': '9c46f3ee1837f6881cb99a52ffecb2760f11dc73', 'versionType': 'git'}, {'status': 'affected', 'version': '0791c0327a6e4e7691d6fc5ad334c215de04dcc9', 'lessThan': 'd90feaa3f74bea8dafb6494631a194c70e547d94', 'versionType': 'git'}, {'status': 'affected', 'version': '0791c0327a6e4e7691d6fc5ad334c215de04dcc9', 'lessThan': '54665dce982689e2fd99b32e9a0dcc204fda8a51', 'versionType': 'git'}], 'programFiles': ['drivers/net/mctp/mctp-usb.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.15'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.15', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.18.36', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.13', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/net/mctp/mctp-usb.c'], 'defaultStatus': 'affected'}]
    Added 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.
    Added Reference https://git.kernel.org/stable/c/54665dce982689e2fd99b32e9a0dcc204fda8a51
    Added Reference https://git.kernel.org/stable/c/9c46f3ee1837f6881cb99a52ffecb2760f11dc73
    Added Reference https://git.kernel.org/stable/c/d90feaa3f74bea8dafb6494631a194c70e547d94
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.