Answer in brief
CVE-2025-38364 records a Unknown severity vulnerability in maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38364 records a Unknown severity vulnerability in maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <d69cd64bd5af41c6fd409313504089970edaf02f || >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <e63032e66bca1d06e600033f3369ba3db3af0870 || >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <cf95f8426f889949b738f51ffcd72884411f3a6a || >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <9e32f4700867abbd5d19abfcf698dbd0d2ce36a4 || >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <fba46a5d83ca8decb338722fb4899026d8d9ead2 | d69cd64bd5af41c6fd409313504089970edaf02f, e63032e66bca1d06e600033f3369ba3db3af0870, cf95f8426f889949b738f51ffcd72884411f3a6a, 9e32f4700867abbd5d19abfcf698dbd0d2ce36a4, fba46a5d83ca8decb338722fb4899026d8d9ead2 |
| Linux/Linuxgeneric | 6.1 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
Published upstream
Jul 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
In the Linux kernel, the following vulnerability has been resolved: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() Temporarily clear the preallocation flag when explicitly requesting allocations. Pre-existing allocations are already counted against the request through mas_node_count_gfp(), but the allocations will not happen if the MA_STATE_PREALLOC flag is set. This flag is meant to avoid re-allocating in bulk allocation mode, and to detect issues with preallocation calculations. The MA_STATE_PREALLOC flag should also always be set on zero allocations so that detection of underflow allocations will print a WARN_ON() during consumption. User visible effect of this flaw is a WARN_ON() followed by a null pointer dereference when subsequent requests for larger number of nodes is ignored, such as the vma merge retry in mmap_region() caused by drivers altering the vma flags (which happens in v6.6, at least)
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <d69cd64bd5af41c6fd409313504089970edaf02f || >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <e63032e66bca1d06e600033f3369ba3db3af0870 || >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <cf95f8426f889949b738f51ffcd72884411f3a6a || >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <9e32f4700867abbd5d19abfcf698dbd0d2ce36a4 || >=54a611b605901c7d5d05b6b8f5d04a6ceb0962aa <fba46a5d83ca8decb338722fb4899026d8d9ead2 | d69cd64bd5af41c6fd409313504089970edaf02f, e63032e66bca1d06e600033f3369ba3db3af0870, cf95f8426f889949b738f51ffcd72884411f3a6a, 9e32f4700867abbd5d19abfcf698dbd0d2ce36a4, fba46a5d83ca8decb338722fb4899026d8d9ead2 |
| Linux/Linuxgeneric | 6.1 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
Published upstream
Jul 25, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
In the Linux kernel, the following vulnerability has been resolved: maple_tree: fix MA_STATE_PREALLOC flag in mas_preallocate() Temporarily clear the preallocation flag when explicitly requesting allocations. Pre-existing allocations are already counted against the request through mas_node_count_gfp(), but the allocations will not happen if the MA_STATE_PREALLOC flag is set. This flag is meant to avoid re-allocating in bulk allocation mode, and to detect issues with preallocation calculations. The MA_STATE_PREALLOC flag should also always be set on zero allocations so that detection of underflow allocations will print a WARN_ON() during consumption. User visible effect of this flaw is a WARN_ON() followed by a null pointer dereference when subsequent requests for larger number of nodes is ignored, such as the vma merge retry in mmap_region() caused by drivers altering the vma flags (which happens in v6.6, at least)
Quoted source text, attributed separately from HOL analysis.