{"vulnerability": "CVE-2024-41021", "sightings": [{"uuid": "d6beba81-8a01-4d9a-a1a6-46ac91d94e00", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-41021", "type": "seen", "source": "https://t.me/cvedetector/1850", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-41021 - IBM s390 Linux Kernel HWPOISON Memory Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-41021 \nPublished : July 29, 2024, 2:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ns390/mm: Fix VM_FAULT_HWPOISON handling in do_exception()  \n  \nThere is no support for HWPOISON, MEMORY_FAILURE, or ARCH_HAS_COPY_MC on  \ns390. Therefore we do not expect to see VM_FAULT_HWPOISON in  \ndo_exception().  \n  \nHowever, since commit af19487f00f3 (\"mm: make PTE_MARKER_SWAPIN_ERROR more  \ngeneral\"), it is possible to see VM_FAULT_HWPOISON in combination with  \nPTE_MARKER_POISONED, even on architectures that do not support HWPOISON  \notherwise. In this case, we will end up on the BUG() in do_exception().  \n  \nFix this by treating VM_FAULT_HWPOISON the same as VM_FAULT_SIGBUS, similar  \nto x86 when MEMORY_FAILURE is not configured. Also print unexpected fault  \nflags, for easier debugging.  \n  \nNote that VM_FAULT_HWPOISON_LARGE is not expected, because s390 cannot  \nsupport swap entries on other levels than PTE level. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T17:07:46.000000Z"}]}