7.8
Advisory Published
Updated

CVE-2024-50222: iov_iter: fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP

First published: Sat Nov 09 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: iov_iter: fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP generic/077 on x86_32 CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP=y with highmem, on huge=always tmpfs, issues a warning and then hangs (interruptibly): WARNING: CPU: 5 PID: 3517 at mm/highmem.c:622 kunmap_local_indexed+0x62/0xc9 CPU: 5 UID: 0 PID: 3517 Comm: cp Not tainted 6.12.0-rc4 #2 ... copy_page_from_iter_atomic+0xa6/0x5ec generic_perform_write+0xf6/0x1b4 shmem_file_write_iter+0x54/0x67 Fix copy_page_from_iter_atomic() by limiting it in that case (include/linux/skbuff.h skb_frag_must_loop() does similar). But going forward, perhaps CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP is too surprising, has outlived its usefulness, and should just be removed?

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel>=6.6<6.6.60
Linux Kernel>=6.7<6.11.7
Linux Kernel=6.12-rc1
Linux Kernel=6.12-rc2
Linux Kernel=6.12-rc3
Linux Kernel=6.12-rc4
Linux Kernel=6.12-rc5
debian/linux
5.10.223-1
5.10.234-1
6.1.129-1
6.1.133-1
6.12.22-1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-50222?

    CVE-2024-50222 is considered a high severity vulnerability due to its potential to cause system hangs and warnings in affected Linux kernels.

  • How do I fix CVE-2024-50222?

    To fix CVE-2024-50222, ensure your system is updated to Linux kernel versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.128-1, 6.12.12-1, or 6.12.16-1 or later.

  • Which systems are affected by CVE-2024-50222?

    CVE-2024-50222 affects Linux kernel versions between 6.7 and 6.6.60, along with specific configurations like CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP.

  • Is there a workaround for CVE-2024-50222?

    Currently, the most effective mitigation for CVE-2024-50222 is to update to the latest fixed kernel version.

  • What can happen if CVE-2024-50222 is exploited?

    Exploitation of CVE-2024-50222 can lead to system instability, causing hangs and interruptions during operations on affected systems.

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203