CVE-2023-52652
What it is
In the Linux kernel, the following vulnerability has been resolved: NTB: fix possible name leak in ntb_register_device() If device_register() fails in ntb_register_device(), the device name allocated by dev_set_name() should be freed. As per the comment in device_register(), callers should use put_device() to give up the reference in the error path. So fix this by calling put_device() in the error path so that the name can be freed in kobject_cleanup(). As a result of this, put_device() in the error path of ntb_register_device() is removed and the actual error is returned. [mani: reworded commit message]
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.3% 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.3% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.153
- Linux Kernel < 6.1.83
- Linux Kernel < 6.6.23
- Linux Kernel < 6.7.11
- Linux Kernel < 6.8.2
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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-52652.md and follow it. Check whether this project is affected by CVE-2023-52652. 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/6632a54ac8057cc0b0d789c6f73883e871bcd25c
- https://git.kernel.org/stable/c/913421f9f7fd8324dcc41753d0f28b52e177ef04
- https://git.kernel.org/stable/c/a039690d323221eb5865f1f31db3ec264e7a14b6
- https://git.kernel.org/stable/c/a62b9f3d7bbfac874cc0c638bc1776dcf1f8ec06
- https://git.kernel.org/stable/c/aebfdfe39b9327a3077d0df8db3beb3160c9bdd0
- https://git.kernel.org/stable/c/e8025439ef8e16029dc313d78a351ef192469b7b
- https://git.kernel.org/stable/c/6632a54ac8057cc0b0d789c6f73883e871bcd25c
- https://git.kernel.org/stable/c/913421f9f7fd8324dcc41753d0f28b52e177ef04
- https://git.kernel.org/stable/c/a039690d323221eb5865f1f31db3ec264e7a14b6
- https://git.kernel.org/stable/c/a62b9f3d7bbfac874cc0c638bc1776dcf1f8ec06
References
- https://git.kernel.org/stable/c/6632a54ac8057cc0b0d789c6f73883e871bcd25c
- https://git.kernel.org/stable/c/913421f9f7fd8324dcc41753d0f28b52e177ef04
- https://git.kernel.org/stable/c/a039690d323221eb5865f1f31db3ec264e7a14b6
- https://git.kernel.org/stable/c/a62b9f3d7bbfac874cc0c638bc1776dcf1f8ec06
- https://git.kernel.org/stable/c/aebfdfe39b9327a3077d0df8db3beb3160c9bdd0
- https://git.kernel.org/stable/c/e8025439ef8e16029dc313d78a351ef192469b7b
- https://git.kernel.org/stable/c/6632a54ac8057cc0b0d789c6f73883e871bcd25c
- https://git.kernel.org/stable/c/913421f9f7fd8324dcc41753d0f28b52e177ef04
- https://git.kernel.org/stable/c/a039690d323221eb5865f1f31db3ec264e7a14b6
- https://git.kernel.org/stable/c/a62b9f3d7bbfac874cc0c638bc1776dcf1f8ec06
- https://git.kernel.org/stable/c/aebfdfe39b9327a3077d0df8db3beb3160c9bdd0
- https://git.kernel.org/stable/c/e8025439ef8e16029dc313d78a351ef192469b7b