In the Linux kernel, the following vulnerability has been resolved:
cgroup/dmem: avoid pool UAF
An UAF issue was observed:
BUG: KASAN: slab-use-after-free in page_counter_uncharge+0x65/0x150
Write of size 8 at addr ffff888106715440 by task insmod/527
CPU: 4 UID: 0 PID: 527 Comm: insmod 6.19.0-rc7-next-20260129+ #11
Tainted: [O]=OOT_MODULE
Call Trace:
<TASK>
dump_stack_lvl+0x82/0xd0
kasan_report+0xca/0x100
kasan_check_range+0x39/0x1c0
page_counter_uncharge+0x65/0x150
dmem_cgroup_uncharge+0x1f/0x260
Allocated by task 527:
Freed by task 0:
The buggy address belongs to the object at ffff888106715400
which belongs to the cache kmalloc-512 of size 512
The buggy address is located 64 bytes inside of
freed 512-byte region [ffff888106715400, ffff888106715600)
The buggy address belongs to the physical page:
Memory state around the buggy address:
ffff888106715300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff888106715380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff888106715400: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff888106715480: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff888106715500: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
The issue occurs because a pool can still be held by a caller after its
associated memory region is unregistered. The current implementation frees
the pool even if users still hold references to it (e.g., before uncharge
operations complete).
This patch adds a reference counter to each pool, ensuring that a pool is
only freed when its reference count drops to zero.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23195 is a high-severity Linux kernel use-after-free in cgroup/dmem. A local authenticated attacker could potentially affect confidentiality, integrity, and availability on vulnerable kernels. The issue is not listed as CISA KEV in the provided sources, so active exploitation is not established here.
Executive priority
Prioritize remediation in the next high-severity kernel patch cycle, especially on multi-user, hosting, CI, or workload-consolidation systems. Immediate emergency action is not supported unless local attacker presence or suspicious kernel crashes are observed.
Technical view
The flaw is in Linux kernel cgroup/dmem pool lifetime handling. A pool may be freed after its memory region is unregistered while callers still hold references, leading to use-after-free during uncharge operations. The cited fix adds pool reference counting so freeing occurs only after references drop to zero.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions or commits identified by the CVE record. Risk increases where local users or untrusted workloads can execute code. Network-only exposure is not supported by the CVSS vector.
Exploitation context
The CVSS vector is local, high complexity, low privileges, and no user interaction. Provided sources do not show public exploitation, weaponized proof of concept, or KEV listing. Treat exploitation feasibility as plausible but not confirmed from this bundle.
Researcher notes
The source evidence identifies a KASAN-detected slab use-after-free in page_counter_uncharge through dmem_cgroup_uncharge. The root cause is pool lifetime mismanagement after memory-region unregister. The fix direction is reference counting, but downstream vendor backport status must be verified separately.
Mitigation direction
Identify Linux hosts running affected kernel versions or commits.
Review the referenced kernel stable commits and vendor advisories.
Apply vendor-supported kernel updates that include the cgroup/dmem fix.
Prioritize shared systems with local users or untrusted workloads.
Use normal change control and reboot planning for kernel updates.
Validation and detection
Inventory running kernel versions across Linux assets.
Map kernel builds to the CVE affected version data.
Confirm whether vendor packages include the referenced stable fixes.
Check for kernel crash reports matching cgroup/dmem use-after-free symptoms.
Document systems deferred from patching and compensating access controls.
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-23195 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.