CVE-2026-23123
Uninitialized Pointer Vulnerability in Linux Kernel debugfs Component
Publication date: 2026-02-14
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.7 (inc) to 6.12.68 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.8 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.6 (inc) to 6.6.122 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-908 | The product uses or accesses a resource that has not been initialized. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's interconnect debugfs component. The issue arises because the variables src_node and dst_node were left uninitialized before being used in the debugfs_create_str() API. This API expects the string pointer to be either NULL or point to valid kmalloc() memory. If the pointer is uninitialized, it can cause problems during reads and writes.
The fix involved initializing src_node and dst_node to empty strings before creating the debugfs entries, ensuring that any reads or writes to these entries are safe.
How can this vulnerability impact me? :
If the src_node and dst_node pointers are uninitialized, it can lead to unsafe reads and writes in the debugfs interface of the Linux kernel. This could potentially cause system instability, crashes, or unexpected behavior when interacting with the debugfs entries related to interconnect.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know