LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23387: pinctrl: cirrus: cs42l43: Fix double-put in cs42l43_pin_probe()

In the Linux kernel, the following vulnerability has been resolved: pinctrl: cirrus: cs42l43: Fix double-put in cs42l43_pin_probe() devm_add_action_or_reset() already invokes the action on failure, so the explicit put causes a double-put.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-23387 is a Linux kernel bug in the Cirrus CS42L43 pin control driver. A failure during device setup can release the same resource twice. The provided sources do not include CVSS, CWE, or exploitation evidence, so business urgency should be based on whether affected kernels and this hardware driver are in use.

Executive priority

Treat this as a targeted kernel maintenance issue, not an emergency based on current evidence. Escalate priority for embedded, audio, or hardware platforms that use CS42L43 support and run listed affected kernels.

Technical view

The flaw is in cs42l43_pin_probe(). devm_add_action_or_reset() already runs the cleanup action when registration fails, but the code also explicitly performs a put, creating a double-put condition on the failure path. The CVE record lists affected Linux kernel versions and references stable kernel commits that resolve it.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the Cirrus CS42L43 pinctrl driver present and relevant hardware or platform support. General internet-facing exposure is not indicated by the provided sources.

Exploitation context

The bundle does not show active exploitation, KEV listing, public exploit details, or a practical attack path. The issue appears tied to driver probe failure handling rather than a remote service surface.

Researcher notes

Evidence is narrow but clear: the bug is a double resource release in a kernel driver error path. Impact severity is not scored in the bundle, so avoid assuming privilege escalation, denial of service, or exploitability without additional vendor analysis.

Mitigation direction

  • Update affected Linux kernels to vendor-provided fixed builds or stable commits.
  • Prioritize systems using Cirrus CS42L43 hardware or pinctrl support.
  • Check distribution advisories for backported kernel fixes.
  • Use normal kernel maintenance windows if the driver is not present or used.

Validation and detection

  • Inventory Linux kernel versions against the CVE affected and fixed version data.
  • Confirm whether CS42L43 pinctrl support is built, available, or loaded.
  • Review vendor kernel changelogs for the referenced stable commits.
  • Document systems where affected versions remain pending patching.
Prepared
Confidence
medium
Sources
7

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-2026-23387 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
6Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9026f31a520d43cc01eb1c08938fc19efadd78cc, 36f91eeffd03f5c52406e0c4e2e0fb040307d00c, 9b07cdf86a0b90556f5b68a6b20b35833b558df3, 9b07cdf86a0b90556f5b68a6b20b35833b558df3, 9b07cdf86a0b90556f5b68a6b20b35833b558df3, d7adbba9298fd74dde0abed5c93312c08c9e6507, 6.6.118, 6.12.60, 6.17.10unaffected
LinuxLinux6.18, 0, 6.6.130, 6.12.77, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

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