LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23129: dpll: Prevent duplicate registrations

In the Linux kernel, the following vulnerability has been resolved: dpll: Prevent duplicate registrations Modify the internal registration helpers dpll_xa_ref_{dpll,pin}_add() to reject duplicate registration attempts. Previously, if a caller attempted to register the same pin multiple times (with the same ops, priv, and cookie) on the same device, the core silently increments the reference count and return success. This behavior is incorrect because if the caller makes these duplicate registrations then for the first one dpll_pin_registration is allocated and for others the associated dpll_pin_ref.refcount is incremented. During the first unregistration the associated dpll_pin_registration is freed and for others WARN is fired. Fix this by updating the logic to return `-EEXIST` if a matching registration is found to enforce a strict "register once" policy.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23129 is a Linux kernel flaw in the DPLL subsystem. Duplicate device or pin registration could be accepted when it should be rejected, leading to incorrect cleanup behavior and kernel warnings during unregister. The public sources do not provide CVSS, confirmed exploitation, or a clear business impact statement.

Executive priority

Treat this as a kernel maintenance item unless your environment depends on DPLL-related hardware. There is no sourced evidence of active exploitation or remote exposure, but kernel defects warrant timely patch validation through normal update channels.

Technical view

The fix changes internal DPLL registration helpers to return -EEXIST when an existing matching registration is found. Previously, duplicate registrations could increment a reference count while only the first allocation represented the registration, causing inconsistent unregister behavior and WARN conditions.

Likely exposure

Exposure appears limited to Linux kernels with DPLL support and relevant drivers or hardware paths. The sources do not indicate a remotely reachable service or broad default exposure. Kernel version and distro backport status must be checked directly.

Exploitation context

The source bundle does not report active exploitation, public exploit use, KEV listing, or weaponized attack paths. Evidence only describes an internal kernel registration logic defect and its correction.

Researcher notes

The public record lacks CVSS, CWE, detailed impact, and exploitability analysis. The safest conclusion is a DPLL core correctness bug with potential operational stability implications, not a confirmed remote compromise path.

Mitigation direction

  • Check vendor kernel advisories for CVE-2026-23129 applicability and fixed package versions.
  • Prioritize updates on systems using DPLL-capable networking, timing, or related hardware.
  • Apply kernel updates that include the referenced stable commits or vendor backports.
  • If immediate patching is unavailable, monitor vendor guidance for supported mitigations.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Map distro kernel packages to the referenced upstream stable fixes.
  • Identify hosts with DPLL-related drivers or hardware enabled.
  • Review kernel logs for relevant WARN events after DPLL driver activity.
Prepared
Confidence
medium
Sources
5

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-2026-23129 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
0ADP providers
4Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9431063ad323ac864750aeba4d304389bc42ca4e, 9431063ad323ac864750aeba4d304389bc42ca4e, 9431063ad323ac864750aeba4d304389bc42ca4eunaffected
LinuxLinux6.7, 0, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

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