LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23314: regulator: bq257xx: Fix device node reference leak in bq257xx_reg_dt_parse_gpio()

In the Linux kernel, the following vulnerability has been resolved: regulator: bq257xx: Fix device node reference leak in bq257xx_reg_dt_parse_gpio() In bq257xx_reg_dt_parse_gpio(), if fails to get subchild, it returns without calling of_node_put(child), causing the device node reference leak.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel resource-leak bug in a regulator driver. If a specific device-tree parsing failure occurs, the code fails to release a device-node reference. The public record does not show remote code execution, privilege escalation, active exploitation, or a CVSS score.

Executive priority

Treat this as routine kernel maintenance unless your fleet includes hardware using this regulator path. It does not currently justify emergency response based on the supplied evidence, but it should be closed through normal kernel patch cycles.

Technical view

In bq257xx_reg_dt_parse_gpio(), an error path returns after failing to get a subchild without calling of_node_put(child). That leaks a device-node reference in the Linux kernel bq257xx regulator code. Kernel stable commit references are provided as fixes.

Likely exposure

Exposure appears limited to Linux systems using affected kernel code paths for the bq257xx regulator driver and device-tree GPIO parsing. The source bundle does not identify affected distributions, appliances, or default configurations, so product-level exposure needs local inventory confirmation.

Exploitation context

The CVE is not listed as KEV in the source bundle, and no cited source claims active exploitation. The described issue is a reference leak triggered by an error path, not a disclosed exploit chain.

Researcher notes

The useful validation focus is reachability: affected kernel revision, bq257xx driver presence, and relevant device-tree parsing. The public description only supports a device-node reference leak; do not infer broader impact without vendor or upstream scoring.

Mitigation direction

  • Update to a Linux kernel build containing the referenced stable fixes.
  • Check your Linux distribution or device vendor advisory for packaged fixed versions.
  • Prioritize embedded or hardware-specific systems using bq257xx regulator support.
  • Track the issue until NVD or vendor scoring clarifies operational severity.

Validation and detection

  • Inventory Linux kernel versions across affected servers, devices, and firmware images.
  • Check whether the bq257xx regulator driver is present or enabled.
  • Compare kernel source or vendor patches against the three referenced stable commits.
  • Review device-tree configurations for bq257xx regulator usage.
  • Document systems where vendor fixed builds are unavailable.
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-2026-23314 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux981dd162b63578aee34b5c68795e246734b76d70, 981dd162b63578aee34b5c68795e246734b76d70, 981dd162b63578aee34b5c68795e246734b76d70unaffected
LinuxLinux6.18, 0, 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.