LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36002: dpll: fix dpll_pin_on_pin_register() for multiple parent pins

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can trigger a warning or crash path when DPLL pin registrations are unwound incorrectly. The described case involves removing the Intel ice driver on systems with an E810T NIC that includes a DPLL device. The sources do not show active exploitation or a remote attack path.

Executive priority

Treat as a targeted kernel stability fix. It matters most for infrastructure with affected NIC hardware and pinned kernels. Without evidence of active exploitation or a remote path, prioritize through normal kernel maintenance unless impacted hardware is business-critical.

Technical view

The bug is in dpll_pin_on_pin_register()/unregister() handling when one pin is registered against multiple parent pins on the same DPLL device. A second unregister can reference already released registration resources. The fix separates registrations by adding the parent pointer as a cookie and using it during lookup.

Likely exposure

Likely limited to Linux systems using affected kernel code paths with DPLL-capable hardware, specifically the documented ice driver and E810T NIC scenario. The source bundle does not establish broad exposure across all Linux deployments.

Exploitation context

CISA KEV status is false, and the provided sources do not cite exploitation in the wild. The described trigger is an operational driver-removal path causing a call trace, not a documented remote or privilege-escalation exploit.

Researcher notes

The public record lacks CVSS, CWE, and detailed affected release ranges. Analysis should avoid assuming exploitability beyond the documented unregister crash path. Patch validation should focus on whether the parent-cookie registration fix is present.

Mitigation direction

  • Apply Linux stable kernel updates containing the referenced fixes.
  • Check distribution advisories for CVE-2024-36002 package status.
  • Prioritize systems using Intel ice driver with E810T NICs.
  • Avoid unnecessary driver removal on potentially affected production hosts.
  • Track vendor guidance if running custom or pinned kernels.

Validation and detection

  • Inventory Linux kernel versions on systems with DPLL-capable NICs.
  • Identify hosts using the ice driver and Intel E810T hardware.
  • Confirm whether referenced stable fixes are present in deployed kernels.
  • Review kernel logs for DPLL or ice removal call traces.
  • Verify vendor kernel packages include CVE-2024-36002 fixes.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-36002 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb27e32e9367dac024cd6f61f22655714f483fd67, b446631f355ece73b13c311dd712c47381a23172, 769324eb35143462542cdb15483cdaf4877bf661unaffected
LinuxLinux6.8.2unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.