Bug 2300398 (CVE-2024-41032) - CVE-2024-41032 kernel: mm: vmalloc: check if a hash-index is in cpu_possible_mask
Summary: CVE-2024-41032 kernel: mm: vmalloc: check if a hash-index is in cpu_possible_...
Keywords:
Status: NEW
Alias: CVE-2024-41032
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2301533
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-29 15:31 UTC by OSIDB Bzimport
Modified: 2024-11-12 09:36 UTC (History)
4 users (show)

Fixed In Version: kernel 6.6.41, kernel 6.9.10, kernel 6.10
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2024:9315 0 None None None 2024-11-12 09:36:34 UTC

Description OSIDB Bzimport 2024-07-29 15:31:37 UTC
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.

Comment 1 Mauro Matteo Cascella 2024-07-30 08:54:36 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024072922-CVE-2024-41032-6284@gregkh/T

Comment 2 Mauro Matteo Cascella 2024-07-30 08:54:56 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2301533]

Comment 6 errata-xmlrpc 2024-11-12 09:36:33 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2024:9315 https://access.redhat.com/errata/RHSA-2024:9315


Note You need to log in before you can comment on or make changes to this bug.