CVE-2026-23260: regmap: maple: free entry on mas_store_gfp() failure
In the Linux kernel, the following vulnerability has been resolved:
regmap: maple: free entry on mas_store_gfp() failure
regcache_maple_write() allocates a new block ('entry') to merge
adjacent ranges and then stores it with mas_store_gfp().
When mas_store_gfp() fails, the new 'entry' remains allocated and
is never freed, leaking memory.
Free 'entry' on the failure path; on success continue freeing the
replaced neighbor blocks ('lower', 'upper').
Security readout for executives and security teams
Plain-English summary
CVE-2026-23260 is a Linux kernel memory leak. A failed internal storage operation can leave an allocated cache block unreleased. The public record does not provide CVSS, CWE, exploitability, or real-world attack evidence, so urgency depends on where affected kernel versions are deployed and vendor backport status.
Executive priority
Treat this as a patch-management item, not an emergency, unless critical systems run affected kernels and show memory pressure. No public source in the bundle supports active exploitation or a high-severity rating.
Technical view
The issue is in regmap maple cache handling. regcache_maple_write() allocates a new entry while merging adjacent ranges, then calls mas_store_gfp(). If that call fails, the new entry is not freed. The fix frees entry on the failure path while preserving existing cleanup for replaced lower and upper blocks.
Likely exposure
Exposure is limited to systems running Linux kernel versions or downstream packages that include the vulnerable regmap maple code and lack the referenced stable fixes. The CVE record lists affected Linux 6.x versions, but distro backports may change practical exposure.
Exploitation context
The source bundle does not report active exploitation, public exploit code, or CISA KEV listing. The described impact is memory leakage on an allocation/store failure path, which may matter most on long-running or memory-constrained systems if the vulnerable path is reachable.
Researcher notes
Evidence is narrow but clear: the defect is a missing free on mas_store_gfp() failure in regcache_maple_write(). Practical impact depends on reachability of that path, allocation failure conditions, and downstream kernel packaging. No exploitability details are provided.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check distribution advisories for CVE-2026-23260 backport status.
Prioritize long-running Linux hosts where kernel memory pressure is operationally significant.
Monitor affected systems for unusual kernel memory growth until remediated.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and images.
Compare deployed kernels with the CVE record and vendor advisories.
Confirm whether the kernel source includes the failure-path free for entry.
Record distro package versions that backport the stable kernel fix.
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-23260 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.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Mar 18, 2026, 17:41 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.