CVE-2024-27027
Last modified
CVE-2024-27027 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: dpll: fix dpll_xa_ref_*_del() for multiple registrations Currently, if there are multiple registrations of the same pin on the same dpll device, following warnings are observed: WARNING: CPU: 5 PID: 2212 at drivers/dpll/dpll_core.c:143 dpll_xa_ref_pin_del.isra.0+0x21e/0x230 WARNING: CPU: 5 PID: 2212 at drivers/dpll/dpll_core.c:223 __dpll_pin_unregister+0x2b3/0x2c0 The problem is, that in both dpll_xa_ref_dpll_del() and dpll_xa_ref_pin_del() registration is only removed from list in case the reference count drops to zero. That is wrong, the registration has to be removed always. To fix this, remove the registration from the list and free it unconditionally, instead of doing it only when the ref reference counter reaches zero.. EPSS estimates a 0.26% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: dpll: fix dpll_xa_ref_*_del() for multiple registrations Currently, if there are multiple registrations of the same pin on the same dpll device, following warnings are observed: WARNING: CPU: 5 PID: 2212 at drivers/dpll/dpll_core.c:143 dpll_xa_ref_pin_del.isra.0+0x21e/0x230 WARNING: CPU: 5 PID: 2212 at drivers/dpll/dpll_core.c:223 __dpll_pin_unregister+0x2b3/0x2c0 The problem is, that in both dpll_xa_ref_dpll_del() and dpll_xa_ref_pin_del() registration is only removed from list in case the reference count drops to zero. That is wrong, the registration has to be removed always. To fix this, remove the registration from the list and free it unconditionally, instead of doing it only when the ref reference counter reaches zero.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.7, < 6.7.11 |
| Linux | Linux Kernel | >= 6.8, < 6.8.2 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2024-27027?
How severe is CVE-2024-27027?
How do I fix CVE-2024-27027?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-27021In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27022In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27023In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27024In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-27025In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27026In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27028In the Linux kernel, the following vulnerability has been re…6.5
- CVE-2024-27029In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2024-2703A vulnerability classified as critical has been found in Ten…8.8
- CVE-2024-27030In the Linux kernel, the following vulnerability has been re…6.3
- CVE-2024-27031In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-27032In the Linux kernel, the following vulnerability has been re…6.3
Are you affected by CVE-2024-27027?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
