LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27027: dpll: fix dpll_xa_ref_*_del() for multiple registrations

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-27027 is a Linux kernel defect in DPLL device registration cleanup. When the same pin is registered multiple times on the same DPLL device, cleanup logic can leave stale list entries and trigger kernel warnings. The public record does not state a direct confidentiality, integrity, or availability impact.

Executive priority

Treat this as a routine kernel maintenance item unless affected systems show DPLL warnings or vendor guidance raises severity. There is not enough public evidence to justify emergency action solely from this bundle.

Technical view

The flaw is in drivers/dpll/dpll_core.c. dpll_xa_ref_dpll_del() and dpll_xa_ref_pin_del() removed registration list entries only when the reference count reached zero. The fix removes and frees the registration unconditionally during deletion. Affected Linux kernel entries include 6.7, 6.7.11, 6.8.2, and 6.9 per the provided record.

Likely exposure

Exposure is most relevant to systems running affected Linux kernels with DPLL functionality or drivers using DPLL pin registration. Distribution kernels may have backported fixes, so package version alone may not prove exposure.

Exploitation context

The source bundle reports no CISA KEV listing, no CVSS score, no CWE, and no cited active exploitation. Evidence supports a kernel correctness and warning condition, but not confirmed real-world exploitation.

Researcher notes

The available evidence is limited to the CVE record and Linux stable commits. No exploitability analysis, CVSS vector, affected distro matrix, or attacker prerequisites are provided. Validate exposure against actual kernel source or vendor backport metadata.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes.
  • Check distribution advisories for backported CVE-2024-27027 fixes.
  • Prioritize systems using DPLL-related hardware or drivers.
  • Monitor kernel logs for DPLL unregister warnings.
  • Avoid direct wrangler or deployment assumptions; follow normal kernel maintenance controls.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Confirm whether vendor kernels include the stable DPLL fixes.
  • Review kernel logs for dpll_core.c warning signatures.
  • Check whether deployed hardware or drivers use DPLL functionality.
  • Track CVE record updates for severity or exploit information.
Prepared
Confidence
medium
Sources
5

Public sources used

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-27027 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
4Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9431063ad323ac864750aeba4d304389bc42ca4e, 9431063ad323ac864750aeba4d304389bc42ca4e, 9431063ad323ac864750aeba4d304389bc42ca4eunaffected
LinuxLinux6.7, 0, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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