CVE-2024-39277: dma-mapping: benchmark: handle NUMA_NO_NODE correctly
Published Jun 21, 2024
·Updated
dma-mapping: benchmark: handle NUMANONODE correctly
Affected Software
17 affected componentsFixes available
Linux Linux kernel<5.11
Linux Linux kernel>=5.15<5.15.161
Linux Linux kernel>=6.1<6.1.93
Linux Linux kernel>=6.6<6.6.33
Linux Linux kernel>=6.9<6.9.4
Linux Linux kernel=6.10.0-rc1
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
Linux Linux kernel>=5.11<5.15.161
Linux Linux kernel>=5.16<6.1.93
Linux Linux kernel>=6.2<6.6.33
Linux Linux kernel>=6.7<6.9.4
Linux Linux kernel=6.10-rc1
Microsoft azl3 kernel 6.6.35.1-4
Microsoft cbl2 kernel 5.15.162.2-1
Microsoft azl3 kernel 6.6.29.1-5
Microsoft cbl2 kernel 5.15.160.1-1
Microsoft cbl2 kernel 5.15.160.1-1
Remediation
Event History
Jun 21, 2024
CVE Published
via MITRE·11:15 AM
Data Sourced
via MITRE·11:15 AM
Description
Aug 5, 2024
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Sep 11, 2024
Data Sourced
via Launchpad·04:24 PM
Description
May 5, 2025
Data Sourced
via Ubuntu·05:21 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2024-39277?
CVE-2024-39277 has been classified as a medium severity vulnerability due to potential impacts on system stability.
2
Which versions of the Linux kernel are affected by CVE-2024-39277?
CVE-2024-39277 affects Linux kernel versions below 5.11, between 5.15 and 5.15.161, between 6.1 and 6.1.93, between 6.6 and 6.6.33, and between 6.9 and 6.9.4.
3
How do I fix CVE-2024-39277?
To mitigate CVE-2024-39277, upgrade to a patched version of the Linux kernel, specifically 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1.
4
What is the impact of exploiting CVE-2024-39277?
Exploitation of CVE-2024-39277 could lead to undefined behavior, including array index out-of-bounds errors, affecting system stability.
5
Is there a workaround for CVE-2024-39277?
There are no official workarounds for CVE-2024-39277, so upgrading to a secure kernel version is recommended.