Answer in brief
CVE-2024-41032 records a Unknown severity vulnerability in mm: vmalloc: check if a hash-index is in cpu_possible_mask. 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 | >=062eacf57ad91b5c272f89dc964fd6dd9715ea7d <28acd531c9a365dac01b32e6bc54aed8c1429bcb || >=062eacf57ad91b5c272f89dc964fd6dd9715ea7d <47f9b6e49b422392fb0e348a65eb925103ba1882 || >=062eacf57ad91b5c272f89dc964fd6dd9715ea7d <a34acf30b19bc4ee3ba2f1082756ea2604c19138 | 28acd531c9a365dac01b32e6bc54aed8c1429bcb, 47f9b6e49b422392fb0e348a65eb925103ba1882, a34acf30b19bc4ee3ba2f1082756ea2604c19138 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Jul 29, 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: mm: vmalloc: check if a hash-index is in cpu_possible_mask The problem is that there are systems where cpu_possible_mask has gaps between set CPUs, for example SPARC. In this scenario addr_to_vb_xa() hash function can return an index which accesses to not-possible and not setup CPU area using per_cpu() macro. This results in an oops on SPARC. A per-cpu vmap_block_queue is also used as hash table, incorrectly assuming the cpu_possible_mask has no gaps. Fix it by adjusting an index to a next possible CPU.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-41032 records a Unknown severity vulnerability in mm: vmalloc: check if a hash-index is in cpu_possible_mask. 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 | >=062eacf57ad91b5c272f89dc964fd6dd9715ea7d <28acd531c9a365dac01b32e6bc54aed8c1429bcb || >=062eacf57ad91b5c272f89dc964fd6dd9715ea7d <47f9b6e49b422392fb0e348a65eb925103ba1882 || >=062eacf57ad91b5c272f89dc964fd6dd9715ea7d <a34acf30b19bc4ee3ba2f1082756ea2604c19138 | 28acd531c9a365dac01b32e6bc54aed8c1429bcb, 47f9b6e49b422392fb0e348a65eb925103ba1882, a34acf30b19bc4ee3ba2f1082756ea2604c19138 |
| Linux/Linuxgeneric | 6.4 | Not reported |
Published upstream
Jul 29, 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: mm: vmalloc: check if a hash-index is in cpu_possible_mask The problem is that there are systems where cpu_possible_mask has gaps between set CPUs, for example SPARC. In this scenario addr_to_vb_xa() hash function can return an index which accesses to not-possible and not setup CPU area using per_cpu() macro. This results in an oops on SPARC. A per-cpu vmap_block_queue is also used as hash table, incorrectly assuming the cpu_possible_mask has no gaps. Fix it by adjusting an index to a next possible CPU.
Quoted source text, attributed separately from HOL analysis.