Answer in brief
CVE-2024-46847 records a Unknown severity vulnerability in mm: vmalloc: ensure vmap_block is initialised before adding to queue. 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 | >=88e0ad40d08a73a74c597e69f4cd2d1fba3838b5 <1b2770e27d6d952f491bb362b657e5b2713c3efd || >=8c61291fd8500e3b35c7ec0c781b273d8cc96cde <6cf74e0e5e3ab5d5c9defb4c73dad54d52224671 || >=8c61291fd8500e3b35c7ec0c781b273d8cc96cde <3e3de7947c751509027d26b679ecd243bc9db255 || 9983b81579be3403f5cc44b11f66c6c8bea6547f || >=6.6.37 <6.6.51 || >=6.9.8 <6.10 | 1b2770e27d6d952f491bb362b657e5b2713c3efd, 6cf74e0e5e3ab5d5c9defb4c73dad54d52224671, 3e3de7947c751509027d26b679ecd243bc9db255, 6.6.51, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Sep 27, 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: ensure vmap_block is initialised before adding to queue Commit 8c61291fd850 ("mm: fix incorrect vbq reference in purge_fragmented_block") extended the 'vmap_block' structure to contain a 'cpu' field which is set at allocation time to the id of the initialising CPU. When a new 'vmap_block' is being instantiated by new_vmap_block(), the partially initialised structure is added to the local 'vmap_block_queue' xarray before the 'cpu' field has been initialised. If another CPU is concurrently walking the xarray (e.g. via vm_unmap_aliases()), then it may perform an out-of-bounds access to the remote queue thanks to an uninitialised index. This has been observed as UBSAN errors in Android: | Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP | | Call trace: | purge_fragmented_block+0x204/0x21c | _vm_unmap_aliases+0x170/0x378 | vm_unmap_aliases+0x1c/0x28 | change_memory_common+0x1dc/0x26c | set_memory_ro+0x18/0x24 | module_enable_ro+0x98/0x238 | do_init_module+0x1b0/0x310 Move the initialisation of 'vb->cpu' in new_vmap_block() ahead of the addition to the xarray.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-46847 records a Unknown severity vulnerability in mm: vmalloc: ensure vmap_block is initialised before adding to queue. 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 | >=88e0ad40d08a73a74c597e69f4cd2d1fba3838b5 <1b2770e27d6d952f491bb362b657e5b2713c3efd || >=8c61291fd8500e3b35c7ec0c781b273d8cc96cde <6cf74e0e5e3ab5d5c9defb4c73dad54d52224671 || >=8c61291fd8500e3b35c7ec0c781b273d8cc96cde <3e3de7947c751509027d26b679ecd243bc9db255 || 9983b81579be3403f5cc44b11f66c6c8bea6547f || >=6.6.37 <6.6.51 || >=6.9.8 <6.10 | 1b2770e27d6d952f491bb362b657e5b2713c3efd, 6cf74e0e5e3ab5d5c9defb4c73dad54d52224671, 3e3de7947c751509027d26b679ecd243bc9db255, 6.6.51, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Sep 27, 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: ensure vmap_block is initialised before adding to queue Commit 8c61291fd850 ("mm: fix incorrect vbq reference in purge_fragmented_block") extended the 'vmap_block' structure to contain a 'cpu' field which is set at allocation time to the id of the initialising CPU. When a new 'vmap_block' is being instantiated by new_vmap_block(), the partially initialised structure is added to the local 'vmap_block_queue' xarray before the 'cpu' field has been initialised. If another CPU is concurrently walking the xarray (e.g. via vm_unmap_aliases()), then it may perform an out-of-bounds access to the remote queue thanks to an uninitialised index. This has been observed as UBSAN errors in Android: | Internal error: UBSAN: array index out of bounds: 00000000f2005512 [#1] PREEMPT SMP | | Call trace: | purge_fragmented_block+0x204/0x21c | _vm_unmap_aliases+0x170/0x378 | vm_unmap_aliases+0x1c/0x28 | change_memory_common+0x1dc/0x26c | set_memory_ro+0x18/0x24 | module_enable_ro+0x98/0x238 | do_init_module+0x1b0/0x310 Move the initialisation of 'vb->cpu' in new_vmap_block() ahead of the addition to the xarray.
Quoted source text, attributed separately from HOL analysis.