CVE-2024-41032: mm: vmalloc: check if a hash-index is in cpu_possible_mask

Published Jul 29, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

mm: vmalloc: check if a hash-index is in cpupossiblemask

The problem is that there are systems where cpupossiblemask has gaps between set CPUs, for example SPARC. In this scenario addrtovbxa() hash function can return an index which accesses to not-possible and not setup CPU area using percpu() macro. This results in an oops on SPARC.

A per-cpu vmapblockqueue is also used as hash table, incorrectly assuming the cpupossiblemask has no gaps. Fix it by adjusting an index to a next possible CPU.

Affected Software

13 affected componentsFixes available
redhat/kernel<6.6.41
6.6.41
redhat/kernel<6.9.10
6.9.10
redhat/kernel<6.10
6.10
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
Linux Linux kernel>=6.4<6.6.41
Linux Linux kernel>=6.7<6.9.10
Linux Linux kernel=6.10-rc1
Linux Linux kernel=6.10-rc2
Linux Linux kernel=6.10-rc3
Linux Linux kernel=6.10-rc4
Linux Linux kernel=6.10-rc5
Linux Linux kernel=6.10-rc6
Linux Linux kernel=6.10-rc7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.6.41
  2. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.9.10
  3. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 6.10
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  5. Configuration

    Apply the fix in mm/vmalloc so addr_to_vb_xa() verifies that the computed hash-index is present in cpu_possible_mask; if not, adjust the index to the next possible CPU before using per_cpu() access.

    Linux kernel mm/vmalloc (addr_to_vb_xa hash index handling) hash-index bounds check against cpu_possible_mask = Adjust hash index to a next possible CPU within cpu_possible_mask (avoid indices for not-possible CPUs)

Event History

Jul 29, 2024
CVE Published
via MITRE·02:31 PM
Data Sourced
via MITRE·02:31 PM
DescriptionSeverity
Data Sourced
via NVD·03:15 PM
Description
Data Sourced
via NVD·03:15 PM
RemedySeverityAffected Software
Dec 19, 2024
Data Sourced
via Ubuntu·12:31 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-41032?

CVE-2024-41032 has a medium severity rating due to its potential impact on the Linux kernel's memory management.

2

How do I fix CVE-2024-41032?

To fix CVE-2024-41032, update your Linux kernel to one of the patched versions including 6.6.41, 6.9.10, 6.10, or specific versions from Debian.

3

What systems are affected by CVE-2024-41032?

CVE-2024-41032 affects systems running specific versions of the Linux kernel, especially those with gaps in cpu_possible_mask.

4

Who is responsible for the patch of CVE-2024-41032?

The patch for CVE-2024-41032 has been released by the Linux kernel maintainers and is available through various distributions.

5

What type of vulnerability is CVE-2024-41032?

CVE-2024-41032 is a memory management vulnerability in the Linux kernel concerning the handling of hash indices related to CPU masks.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203