mctp: perform route lookups under a RCU read-side lock
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1db0724a01b558feb1ecae551782add1951a114a, Kernel 2405f64a95a7a094eb24cba9bcfaffd1ea264de4, Kernel 5093bbfc10ab6636b32728e35813cbd79feb063c and 1 more.
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 <rootlab@huawei.com>, where introducing a delay in the route lookup could cause a UAF on simultaneous sendmsg() and route deletion.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.15, >=889b7da23abf92faf34491df95733bda63639e32 <1db0724a01b558feb1ecae551782add1951a114a, >=889b7da23abf92faf34491df95733bda63639e32 <2405f64a95a7a094eb24cba9bcfaffd1ea264de4, >=889b7da23abf92faf34491df95733bda63639e32 <5093bbfc10ab6636b32728e35813cbd79feb063c, >=889b7da23abf92faf34491df95733bda63639e32 <6c52b12159049046483fdb0c411a0a1869c41a67 | 1db0724a01b558feb1ecae551782add1951a114a, 2405f64a95a7a094eb24cba9bcfaffd1ea264de4, 5093bbfc10ab6636b32728e35813cbd79feb063c, 6c52b12159049046483fdb0c411a0a1869c41a67 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket