Answer in brief
CVE-2024-36019 records a Unknown severity vulnerability in regmap: maple: Fix cache corruption in regcache_maple_drop(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f033c26de5a5734625d2dd1dc196745fae186f1b <3af6c5ac72dc5b721058132a0a1d7779e443175e || >=f033c26de5a5734625d2dd1dc196745fae186f1b <51c4440b9d3fd7c8234e6de9170a487c03506e53 || >=f033c26de5a5734625d2dd1dc196745fae186f1b <00bb549d7d63a21532e76e4a334d7807a54d9f31 | 3af6c5ac72dc5b721058132a0a1d7779e443175e, 51c4440b9d3fd7c8234e6de9170a487c03506e53, 00bb549d7d63a21532e76e4a334d7807a54d9f31 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
May 30, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: regmap: maple: Fix cache corruption in regcache_maple_drop() When keeping the upper end of a cache block entry, the entry[] array must be indexed by the offset from the base register of the block, i.e. max - mas.index. The code was indexing entry[] by only the register address, leading to an out-of-bounds access that copied some part of the kernel memory over the cache contents. This bug was not detected by the regmap KUnit test because it only tests with a block of registers starting at 0, so mas.index == 0.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-36019 records a Unknown severity vulnerability in regmap: maple: Fix cache corruption in regcache_maple_drop(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f033c26de5a5734625d2dd1dc196745fae186f1b <3af6c5ac72dc5b721058132a0a1d7779e443175e || >=f033c26de5a5734625d2dd1dc196745fae186f1b <51c4440b9d3fd7c8234e6de9170a487c03506e53 || >=f033c26de5a5734625d2dd1dc196745fae186f1b <00bb549d7d63a21532e76e4a334d7807a54d9f31 | 3af6c5ac72dc5b721058132a0a1d7779e443175e, 51c4440b9d3fd7c8234e6de9170a487c03506e53, 00bb549d7d63a21532e76e4a334d7807a54d9f31 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
May 30, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: regmap: maple: Fix cache corruption in regcache_maple_drop() When keeping the upper end of a cache block entry, the entry[] array must be indexed by the offset from the base register of the block, i.e. max - mas.index. The code was indexing entry[] by only the register address, leading to an out-of-bounds access that copied some part of the kernel memory over the cache contents. This bug was not detected by the regmap KUnit test because it only tests with a block of registers starting at 0, so mas.index == 0.
Quoted source text, attributed separately from HOL analysis.