First published: Wed Mar 06 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.119-1 6.12.10-1 6.12.11-1 | |
Linux Kernel | <4.19.307 | |
Linux Kernel | >=4.20<5.4.269 | |
Linux Kernel | >=5.5<5.10.210 | |
Linux Kernel | >=5.11<5.15.149 | |
Linux Kernel | >=5.16<6.1.77 | |
Linux Kernel | >=6.2<6.6.16 | |
Linux Kernel | >=6.7<6.7.4 | |
Debian Debian Linux | =10.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2023-52583 is classified as low because the deadcode is never used.
To fix CVE-2023-52583, ensure you update to the patched Linux kernel versions such as 5.10.223-1 or newer.
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.
CVE-2023-52583 addresses an issue related to incorrect lock order in the Linux kernel, specifically regarding dentry management.
As of now, there are no indications that CVE-2023-52583 is being actively exploited in the wild.