Linux Kernel up to 6.9.11/6.10.1 VM_FAULT_HWPOISON do_exception memory corruption

Summaryinfo

A vulnerability classified as critical was found in Linux Kernel up to 6.9.11/6.10.1. This issue affects the function do_exception of the component VM_FAULT_HWPOISON Handler. Executing a manipulation can lead to memory corruption. This vulnerability is registered as CVE-2024-41021. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 6.9.11/6.10.1 and classified as critical. This vulnerability affects the function do_exception of the component VM_FAULT_HWPOISON Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: s390/mm: Fix VM_FAULT_HWPOISON handling in do_exception() There is no support for HWPOISON, MEMORY_FAILURE, or ARCH_HAS_COPY_MC on s390. Therefore we do not expect to see VM_FAULT_HWPOISON in do_exception(). However, since commit af19487f00f3 ("mm: make PTE_MARKER_SWAPIN_ERROR more general"), it is possible to see VM_FAULT_HWPOISON in combination with PTE_MARKER_POISONED, even on architectures that do not support HWPOISON otherwise. In this case, we will end up on the BUG() in do_exception(). Fix this by treating VM_FAULT_HWPOISON the same as VM_FAULT_SIGBUS, similar to x86 when MEMORY_FAILURE is not configured. Also print unexpected fault flags, for easier debugging. Note that VM_FAULT_HWPOISON_LARGE is not expected, because s390 cannot support swap entries on other levels than PTE level.

The advisory is available at git.kernel.org. This vulnerability was named CVE-2024-41021 since 07/12/2024. The exploitation appears to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 09/25/2025).

The vulnerability scanner Nessus provides a plugin with the ID 210060 (Ubuntu 22.04 LTS / 24.04 LTS : Linux kernel kernel vulnerabilities (USN-7089-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.9.12 or 6.10.2 eliminates this vulnerability. Applying the patch 9e13767ccefd/a3aefb871222/df39038cd895 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (210060) and CERT Bund (WID-SEC-2024-1722). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• IBM InfoSphere Guardium
• Oracle Linux
• NetApp FAS
• NetApp ActiveIQ Unified Manager
• Siemens SIMATIC S7
• Oracle VM
• IBM Security Guardium
• RESF Rocky Linux
• Broadcom Brocade SANnav
• Dell PowerScale
• Open Source Linux Kernel
• IBM QRadar SIEM
• Dell integrated Dell Remote Access Controller
• Dell Avamar
• IBM Storage Scale
• IBM Spectrum Protect Plus
• Juniper Junos Space
• IBM Storage Scale System
• SolarWinds Security Event Manager
• Dell PowerProtect Data Domain
• Dell PowerProtect Data Domain Management Center
• Dell PowerProtect Data Domain OS

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 6.9.0
• 6.9.1
• 6.9.2
• 6.9.3
• 6.9.4
• 6.9.5
• 6.9.6
• 6.9.7
• 6.9.8
• 6.9.9
• 6.9.10
• 6.9.11
• 6.10.0
• 6.10.1

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion