VDB

CVE-2024-46847

CVE-2024-46847 PUBLISHED CVSS 7.8 HIGH

mm: vmalloc: ensure vmap_block is initialised before adding to queue

Reported by linux · Published September 27, 2024

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
LinuxLinux6.10, 6.6.51

Risk scores

CVSS 3.1
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
LinuxLinux88e0ad40d08a73a74c597e69f4cd2d1fba3838b5, 8c61291fd8500e3b35c7ec0c781b273d8cc96cde, 8c61291fd8500e3b35c7ec0c781b273d8cc96cde
LinuxLinux6.10, 0, 6.6.51
LinuxLinux6.9.8, 6.6.51, 6.10.10
linuxlinux_kernel6.10, 6.9.8, 6.10

Timeline

  • Sep 27, 2024 CVE Published
  • Sep 27, 2024 PoC Published
  • Sep 28, 2024 EPSS Score (30 in total, the first dated here)
  • Oct 5, 2024 Coalition ESS Score (9 in total, the first dated here)
  • Jan 4, 2026 Security Advisory (143 in total, the first dated here)
  • May 28, 2026 Distribution Patch (123 in total, the first dated here)
  • Aug 5, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2024-46847
vulnetix vdb fixes CVE-2024-46847

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2024-46847/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›