CVE-2023-52483
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 5.15.137
- Linux Kernel < 6.1.59
- Linux Kernel < 6.5.8
- Linux Kernel 6.6
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2023-52483.md and follow it. Check whether this project is affected by CVE-2023-52483. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/1db0724a01b558feb1ecae551782add1951a114a
- https://git.kernel.org/stable/c/2405f64a95a7a094eb24cba9bcfaffd1ea264de4
- https://git.kernel.org/stable/c/5093bbfc10ab6636b32728e35813cbd79feb063c
- https://git.kernel.org/stable/c/6c52b12159049046483fdb0c411a0a1869c41a67
- https://git.kernel.org/stable/c/1db0724a01b558feb1ecae551782add1951a114a
- https://git.kernel.org/stable/c/2405f64a95a7a094eb24cba9bcfaffd1ea264de4
- https://git.kernel.org/stable/c/5093bbfc10ab6636b32728e35813cbd79feb063c
- https://git.kernel.org/stable/c/6c52b12159049046483fdb0c411a0a1869c41a67
References
- https://git.kernel.org/stable/c/1db0724a01b558feb1ecae551782add1951a114a
- https://git.kernel.org/stable/c/2405f64a95a7a094eb24cba9bcfaffd1ea264de4
- https://git.kernel.org/stable/c/5093bbfc10ab6636b32728e35813cbd79feb063c
- https://git.kernel.org/stable/c/6c52b12159049046483fdb0c411a0a1869c41a67
- https://git.kernel.org/stable/c/1db0724a01b558feb1ecae551782add1951a114a
- https://git.kernel.org/stable/c/2405f64a95a7a094eb24cba9bcfaffd1ea264de4
- https://git.kernel.org/stable/c/5093bbfc10ab6636b32728e35813cbd79feb063c
- https://git.kernel.org/stable/c/6c52b12159049046483fdb0c411a0a1869c41a67