LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23123: interconnect: debugfs: initialize src_node and dst_node to empty strings

In the Linux kernel, the following vulnerability has been resolved: interconnect: debugfs: initialize src_node and dst_node to empty strings The debugfs_create_str() API assumes that the string pointer is either NULL or points to valid kmalloc() memory. Leaving the pointer uninitialized can cause problems. Initialize src_node and dst_node to empty strings before creating the debugfs entries to guarantee that reads and writes are safe.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel defect in an interconnect debug filesystem interface. Two string pointers were not initialized before debugfs entries were created, which could make reads or writes unsafe. Public data does not provide a CVSS score, impact class, or exploitation evidence.

Executive priority

Track this as a kernel maintenance item until vendor severity guidance is available. Prioritize systems with exposed debug or operational interfaces, but do not treat it as confirmed emergency exploitation based on this bundle.

Technical view

The interconnect debugfs code left src_node and dst_node uninitialized before calling debugfs_create_str(). The API expects NULL or valid kmalloc() memory. The resolved change initializes both fields to empty strings so debugfs read and write handling uses safe string storage.

Likely exposure

Potential exposure is limited to Linux systems running affected kernel versions with the interconnect debugfs code present. The bundle does not state remote reachability, required privileges, or whether debugfs must be mounted or accessible.

Exploitation context

The CVE is not listed as KEV, and the supplied sources do not report active exploitation or public exploit details. The practical exploitability and security impact are unclear from the available record.

Researcher notes

Evidence supports a memory-safety fix around debugfs string pointer initialization, but not a complete impact assessment. Validate affected branches through kernel or distribution advisories before assigning exploitability, asset priority, or compensating controls.

Mitigation direction

  • Identify Linux kernel versions across affected fleets.
  • Compare deployed kernels against the CVE record and referenced stable commits.
  • Apply vendor or distribution kernel updates when available.
  • Review vendor advisories for branch-specific fixed versions.
  • Restrict debugfs exposure according to existing hardening policy.

Validation and detection

  • Confirm whether deployed kernels include the referenced stable fixes.
  • Check distribution security advisories for CVE-2026-23123 coverage.
  • Inventory systems where debugfs is mounted or operationally exposed.
  • Verify kernel update status after patch deployment.
  • Document any systems deferred from kernel remediation.
Prepared
Confidence
medium
Sources
6

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-23123 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
5Source 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
LinuxLinux770c69f037c18cfaa37c3d6c6ef8bd257635513f, 770c69f037c18cfaa37c3d6c6ef8bd257635513f, 770c69f037c18cfaa37c3d6c6ef8bd257635513f, 770c69f037c18cfaa37c3d6c6ef8bd257635513funaffected
LinuxLinux6.6, 0, 6.6.122, 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.