CVE-2026-63874

Last refreshed2026-10-30

Status: UPDATED | Advisory ID: CVE-2026-63874

Key Details

CVE	CVE-2026-63874
CVSS Score / Version	7.8 (High) / CVSS v3.1
Updated	2026-10-30
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Linux Kernel
Classified as	CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

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. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-63874
CVE	https://www.cve.org/CVERecord?id=CVE-2026-63874

Source

Reference

NVD

CVE