CVE-2023-52583: ceph: fix deadlock or deadcode of misusing dget()
In the Linux kernel, the following vulnerability has been resolved:
ceph: fix deadlock or deadcode of misusing dget()
The lock order is incorrect between denty and its parent, we should always make sure that the parent get the lock first.
But since this deadcode is never used and the parent dir will always be set from the callers, let's just remove it.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
Event History
Frequently Asked Questions
What is the severity of CVE-2023-52583?
The severity of CVE-2023-52583 is classified as low because the deadcode is never used.
How do I fix CVE-2023-52583?
To fix CVE-2023-52583, ensure you update to the patched Linux kernel versions such as 5.10.223-1 or newer.
What systems are affected by CVE-2023-52583?
CVE-2023-52583 affects various versions of the Linux kernel including those within the ranges of 4.19 up to certain versions of 6.7.
What vulnerabilities does CVE-2023-52583 address?
CVE-2023-52583 addresses an issue related to incorrect lock order in the Linux kernel, specifically regarding dentry management.
Is CVE-2023-52583 being actively exploited?
As of now, there are no indications that CVE-2023-52583 is being actively exploited in the wild.