CVE-2026-23183
NULL Pointer Dereference in Linux Kernel cgroup/dmem Component
Publication date: 2026-02-14
Last updated on: 2026-02-14
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.0-rc6-next-2026012 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's cgroup/dmem subsystem. It is caused by a NULL pointer dereference when setting the maximum limit (max) for a memory region. Specifically, the issue occurs when an invalid or missing check on the options after parsing the region name allows a NULL pointer to be dereferenced, leading to a kernel crash (BUG: kernel NULL pointer dereference).
The problem was triggered by commands like "echo test/region0 > dmem.max" without proper validation, causing the kernel to attempt to access memory at address 0x0, which is invalid.
The fix involved adding a check to ensure the options are valid after parsing the region name to prevent the NULL pointer dereference.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a NULL pointer dereference, resulting in a denial of service (DoS) condition. An attacker or user with the ability to set memory cgroup limits could exploit this to crash the system or cause instability.
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?
This vulnerability is triggered by a NULL pointer dereference in the Linux kernel when setting the max value in cgroup/dmem. It can be detected by observing kernel oops messages or crashes related to NULL pointer dereferences in the cgroup/dmem subsystem.
A specific command that may trigger the issue is writing to the dmem.max file, for example:
- echo test/region0 > dmem.max
Monitoring kernel logs (e.g., using dmesg or journalctl) for messages similar to the provided kernel oops trace can help detect if the vulnerability has been triggered.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that the Linux kernel is updated to a version where the fix has been applied. The fix involves adding a check to validate options after parsing the region_name to prevent NULL pointer dereference.
Until the kernel is updated, avoid setting the max value in cgroup/dmem with invalid or unvalidated inputs, such as using commands like "echo test/region0 > dmem.max".