CVE-2023-54135: maple_tree: fix potential out-of-bounds access in mas_wr_end_piv()
In the Linux kernel, the following vulnerability has been resolved:
maple_tree: fix potential out-of-bounds access in mas_wr_end_piv()
Check the write offset end bounds before using it as the offset into the
pivot array. This avoids a possible out-of-bounds access on the pivot
array if the write extends to the last slot in the node, in which case the
node maximum should be used as the end pivot.
akpm: this doesn't affect any current callers, but new users of mapletree
may encounter this problem if backported into earlier kernels, so let's
fix it in -stable kernels in case of this.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-safety fix in the maple tree data structure. The flaw could allow an out-of-bounds access in a specific write-end pivot calculation. The source notes it does not affect current callers, but Linux still backported the fix to stable kernels for future or backported users.
Executive priority
Treat this as a routine kernel hygiene issue unless vendor advisories identify reachable impact in your environment. There is no cited exploitation and the source says current callers are unaffected, but kernel fixes should not be ignored in standard maintenance cycles.
Technical view
The bug is in mas_wr_end_piv(), where the write offset end could be used as an index into the pivot array before bounds checking. If a write extended to the last node slot, code should use the node maximum as the end pivot instead of indexing beyond the pivot array.
Likely exposure
Exposure appears limited to Linux kernel builds containing the affected maple tree code, especially stable versions identified in the CVE bundle. The source does not identify specific distributions, products, configurations, or reachable subsystems, so exposure must be validated against actual kernel versions and vendor advisories.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. The kernel note says current callers are not affected, which lowers immediate concern, but the memory-safety nature still warrants tracking and routine patching.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploitability analysis, or affected configuration detail is provided. Research should focus on mapping the maple tree commit lineage, identifying which stable and distribution kernels include the fix, and confirming whether any downstream backports introduced relevant callers.
Mitigation direction
Check Linux vendor advisories for fixed kernel packages.
Prioritize kernels matching the affected versions in the CVE record.
Apply stable kernel updates that include the referenced maple_tree fixes.
If patching is delayed, monitor vendor guidance for temporary mitigations.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, appliances, and containers hosts.
Compare running kernels against vendor advisories and the CVE fixed versions.
Confirm whether deployed kernels include one of the referenced stable commits.
Record exceptions where vendor backports fix the issue without changing version numbers.
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-2023-54135 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.
Dec 24, 2025, 13:06 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.