Answer in brief
CVE-2023-52483 records a High severity (CVSS 7.8) vulnerability in mctp: perform route lookups under a RCU read-side lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=889b7da23abf92faf34491df95733bda63639e32 <6c52b12159049046483fdb0c411a0a1869c41a67 || >=889b7da23abf92faf34491df95733bda63639e32 <1db0724a01b558feb1ecae551782add1951a114a || >=889b7da23abf92faf34491df95733bda63639e32 <2405f64a95a7a094eb24cba9bcfaffd1ea264de4 || >=889b7da23abf92faf34491df95733bda63639e32 <5093bbfc10ab6636b32728e35813cbd79feb063c | 6c52b12159049046483fdb0c411a0a1869c41a67, 1db0724a01b558feb1ecae551782add1951a114a, 2405f64a95a7a094eb24cba9bcfaffd1ea264de4, 5093bbfc10ab6636b32728e35813cbd79feb063c |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Feb 29, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-52483 records a High severity (CVSS 7.8) vulnerability in mctp: perform route lookups under a RCU read-side lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc2:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc3:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc4:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.6:rc5:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=889b7da23abf92faf34491df95733bda63639e32 <6c52b12159049046483fdb0c411a0a1869c41a67 || >=889b7da23abf92faf34491df95733bda63639e32 <1db0724a01b558feb1ecae551782add1951a114a || >=889b7da23abf92faf34491df95733bda63639e32 <2405f64a95a7a094eb24cba9bcfaffd1ea264de4 || >=889b7da23abf92faf34491df95733bda63639e32 <5093bbfc10ab6636b32728e35813cbd79feb063c | 6c52b12159049046483fdb0c411a0a1869c41a67, 1db0724a01b558feb1ecae551782add1951a114a, 2405f64a95a7a094eb24cba9bcfaffd1ea264de4, 5093bbfc10ab6636b32728e35813cbd79feb063c |
| Linux/Linuxgeneric | 5.15 | Not reported |
Published upstream
Feb 29, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.