CVE-2024-36002: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: dpll: fix dpll_pin_on_pin_register() for multiple parent pins In scenario where pin is registered with multiple parent pins via dpll_pin_on_pin_register(..), all belonging to the same dpll device. A second call to dpll_pin_on_pin_unregister(..) would cause a call trace, as it tries to use already released registration resources (due to fix introduced in b446631f355e). In this scenario pin was registered twice, so resources are not yet expected to be release until each registered pin/pin pair is unregistered. Currently, the following crash/call trace is produced when ice driver is removed on the system with installed E810T NIC which includes dpll device: WARNING: CPU: 51 PID: 9155 at drivers/dpll/dpll_core.c:809 dpll_pin_ops+0x20/0x30 RIP: 0010:dpll_pin_ops+0x20/0x30 Call Trace: ? __warn+0x7f/0x130 ? dpll_pin_ops+0x20/0x30 dpll_msg_add_pin_freq+0x37/0x1d0 dpll_cmd_pin_get_one+0x1c0/0x400 ? __nlmsg_put+0x63/0x80 dpll_pin_event_send+0x93/0x140 dpll_pin_on_pin_unregister+0x3f/0x100 ice_dpll_deinit_pins+0xa1/0x230 [ice] ice_remove+0xf1/0x210 [ice] Fix by adding a parent pointer as a cookie when creating a registration, also when searching for it. For the regular pins pass NULL, this allows to create separated registration for each parent the pin is registered with.
AI Analysis
Technical Summary
CVE-2024-36002 is a vulnerability identified in the Linux kernel's DPLL (Digital Phase-Locked Loop) subsystem, specifically related to the handling of pin registration and unregistration when multiple parent pins are involved. The issue arises in the function dpll_pin_on_pin_register(), which registers pins with multiple parent pins belonging to the same DPLL device. Due to improper management of registration resources, a second call to dpll_pin_on_pin_unregister() attempts to release resources that have already been freed, leading to a kernel call trace and potential crash. This problem manifests notably when the ice network driver is removed on systems equipped with Intel E810T NICs that include a DPLL device. The crash is caused by the dpll_pin_ops function attempting to operate on invalid memory, as indicated by the kernel warning and call trace logs. The root cause is that the pin was registered twice without proper separation of registration contexts for each parent pin, causing premature resource release. The fix involves adding a parent pointer as a cookie during registration and lookup, allowing distinct registrations for each parent pin and preventing double-free scenarios. This vulnerability affects specific Linux kernel versions identified by their commit hashes and has been publicly disclosed but currently has no known exploits in the wild. The vulnerability does not require user interaction but is triggered by driver removal operations involving the affected hardware and kernel subsystem.
Potential Impact
For European organizations, this vulnerability primarily threatens systems running affected Linux kernel versions with Intel E810T NICs or similar hardware utilizing the DPLL subsystem. The impact includes potential kernel crashes leading to denial of service (DoS) conditions, which can disrupt critical network infrastructure, especially in data centers, telecommunications, and cloud service providers relying on these NICs. Such disruptions can affect availability of services and may require system reboots, causing downtime and operational impact. While this vulnerability does not directly lead to privilege escalation or data leakage, the instability it causes can be exploited by attackers to degrade service reliability or as part of a larger attack chain. Organizations with high availability requirements or those operating critical infrastructure should be particularly cautious. The lack of known exploits reduces immediate risk, but the presence of a kernel-level bug affecting hardware drivers means that targeted attacks or accidental triggers could cause significant operational issues.
Mitigation Recommendations
European organizations should promptly apply the patch that fixes this vulnerability by updating their Linux kernel to versions that include the fix for CVE-2024-36002. Since the vulnerability is tied to specific hardware (Intel E810T NICs) and the ice driver, organizations should audit their systems to identify affected devices and kernel versions. If immediate patching is not feasible, temporarily avoiding removal or reloading of the ice driver can reduce the risk of triggering the crash. Additionally, monitoring kernel logs for warnings related to dpll_pin_ops or ice driver removal can help detect attempts to exploit or accidentally trigger the issue. For environments where uptime is critical, consider implementing redundancy and failover mechanisms to mitigate potential downtime caused by kernel crashes. Coordination with hardware vendors and Linux distribution maintainers for timely updates and guidance is also recommended. Finally, ensure that system administrators are aware of this vulnerability and trained to handle driver-related issues safely.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-36002: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: dpll: fix dpll_pin_on_pin_register() for multiple parent pins In scenario where pin is registered with multiple parent pins via dpll_pin_on_pin_register(..), all belonging to the same dpll device. A second call to dpll_pin_on_pin_unregister(..) would cause a call trace, as it tries to use already released registration resources (due to fix introduced in b446631f355e). In this scenario pin was registered twice, so resources are not yet expected to be release until each registered pin/pin pair is unregistered. Currently, the following crash/call trace is produced when ice driver is removed on the system with installed E810T NIC which includes dpll device: WARNING: CPU: 51 PID: 9155 at drivers/dpll/dpll_core.c:809 dpll_pin_ops+0x20/0x30 RIP: 0010:dpll_pin_ops+0x20/0x30 Call Trace: ? __warn+0x7f/0x130 ? dpll_pin_ops+0x20/0x30 dpll_msg_add_pin_freq+0x37/0x1d0 dpll_cmd_pin_get_one+0x1c0/0x400 ? __nlmsg_put+0x63/0x80 dpll_pin_event_send+0x93/0x140 dpll_pin_on_pin_unregister+0x3f/0x100 ice_dpll_deinit_pins+0xa1/0x230 [ice] ice_remove+0xf1/0x210 [ice] Fix by adding a parent pointer as a cookie when creating a registration, also when searching for it. For the regular pins pass NULL, this allows to create separated registration for each parent the pin is registered with.
AI-Powered Analysis
Technical Analysis
CVE-2024-36002 is a vulnerability identified in the Linux kernel's DPLL (Digital Phase-Locked Loop) subsystem, specifically related to the handling of pin registration and unregistration when multiple parent pins are involved. The issue arises in the function dpll_pin_on_pin_register(), which registers pins with multiple parent pins belonging to the same DPLL device. Due to improper management of registration resources, a second call to dpll_pin_on_pin_unregister() attempts to release resources that have already been freed, leading to a kernel call trace and potential crash. This problem manifests notably when the ice network driver is removed on systems equipped with Intel E810T NICs that include a DPLL device. The crash is caused by the dpll_pin_ops function attempting to operate on invalid memory, as indicated by the kernel warning and call trace logs. The root cause is that the pin was registered twice without proper separation of registration contexts for each parent pin, causing premature resource release. The fix involves adding a parent pointer as a cookie during registration and lookup, allowing distinct registrations for each parent pin and preventing double-free scenarios. This vulnerability affects specific Linux kernel versions identified by their commit hashes and has been publicly disclosed but currently has no known exploits in the wild. The vulnerability does not require user interaction but is triggered by driver removal operations involving the affected hardware and kernel subsystem.
Potential Impact
For European organizations, this vulnerability primarily threatens systems running affected Linux kernel versions with Intel E810T NICs or similar hardware utilizing the DPLL subsystem. The impact includes potential kernel crashes leading to denial of service (DoS) conditions, which can disrupt critical network infrastructure, especially in data centers, telecommunications, and cloud service providers relying on these NICs. Such disruptions can affect availability of services and may require system reboots, causing downtime and operational impact. While this vulnerability does not directly lead to privilege escalation or data leakage, the instability it causes can be exploited by attackers to degrade service reliability or as part of a larger attack chain. Organizations with high availability requirements or those operating critical infrastructure should be particularly cautious. The lack of known exploits reduces immediate risk, but the presence of a kernel-level bug affecting hardware drivers means that targeted attacks or accidental triggers could cause significant operational issues.
Mitigation Recommendations
European organizations should promptly apply the patch that fixes this vulnerability by updating their Linux kernel to versions that include the fix for CVE-2024-36002. Since the vulnerability is tied to specific hardware (Intel E810T NICs) and the ice driver, organizations should audit their systems to identify affected devices and kernel versions. If immediate patching is not feasible, temporarily avoiding removal or reloading of the ice driver can reduce the risk of triggering the crash. Additionally, monitoring kernel logs for warnings related to dpll_pin_ops or ice driver removal can help detect attempts to exploit or accidentally trigger the issue. For environments where uptime is critical, consider implementing redundancy and failover mechanisms to mitigate potential downtime caused by kernel crashes. Coordination with hardware vendors and Linux distribution maintainers for timely updates and guidance is also recommended. Finally, ensure that system administrators are aware of this vulnerability and trained to handle driver-related issues safely.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-05-17T13:50:33.149Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9821c4522896dcbddcdd
Added to database: 5/21/2025, 9:08:49 AM
Last enriched: 6/28/2025, 3:27:28 AM
Last updated: 8/6/2025, 9:05:00 AM
Views: 17
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.