CVE-2023-52483

mctp: perform route lookups under a RCU read-side lock

HIGH
7.8
CVSS Score
Published: February 29, 2024 at 05:43 AM UTC
Updated: August 5, 2026 at 09:24 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: mctp: perform route lookups under a RCU read-side lock Our current route lookups (mctp_route_lookup and mctp_route_lookup_null) traverse the net's route list without the RCU read lock held. This means the route lookup is subject to preemption, resulting in an potential grace period expiry, and so an eventual kfree() while we still have the route pointer. Add the proper read-side critical section locks around the route lookups, preventing premption and a possible parallel kfree. The remaining net->mctp.routes accesses are already under a rcu_read_lock, or protected by the RTNL for updates. Based on an analysis from Sili Luo <[email protected]>, where introducing a delay in the route lookup could cause a UAF on simultaneous sendmsg() and route deletion.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15 ≤ v < 5.15.1375.15 ≤ v < 6.1.595.15 ≤ v < 6.5.85.15 ≤ v < 6.65.16 ≤ v < 6.1.596.2 ≤ v < 6.5.86.6 rc16.6 rc26.6 rc36.6 rc46.6 rc5889b7da23abf92faf34491df95733bda63639e32
Vendor states this is fixed in 1db0724a01b558feb1ecae551782add1951a114a (fixed)
Vendor states this is fixed in 2405f64a95a7a094eb24cba9bcfaffd1ea264de4 (fixed)
Vendor states this is fixed in 5093bbfc10ab6636b32728e35813cbd79feb063c (fixed)
Vendor states this is fixed in 6c52b12159049046483fdb0c411a0a1869c41a67 (fixed)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.15.137 (unaffected)
Vendor states this is fixed in 6.1.59 (unaffected)
Vendor states this is fixed in 6.5.8 (unaffected)
Vendor states this is fixed in 6.6 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/1db0724a01b558feb1ecae551782add1951a114a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2405f64a95a7a094eb24cba9bcfaffd1ea264de4
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5093bbfc10ab6636b32728e35813cbd79feb063c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6c52b12159049046483fdb0c411a0a1869c41a67

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card