CVE-2024-50222: iov_iter: fix copy_page_from_iter_atomic() if KMAP_LOCAL_FORCE_MAP
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?
Security readout for executives and security teams
Plain-English summary
A Linux kernel memory-mapping error can trigger a warning and an interruptible system hang during certain file writes. The documented failure requires a specialized 32-bit x86, high-memory debug configuration and huge-page-backed tmpfs, so typical modern systems may have limited exposure. The supplied CVSS rating is 7.8, but the sources do not document real-world attacks.
Executive priority
Treat as high priority where the documented configuration exists because a local user may cause serious system impact. Use configuration-based triage rather than an indiscriminate emergency rollout. Systems without the specialized conditions appear less likely to encounter the documented failure, although complete affected-version boundaries should be confirmed with vendors.
Technical view
The flaw affects copy_page_from_iter_atomic() when CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP is enabled. Under the documented x86_32 highmem and huge=always tmpfs conditions, incorrect local mapping handling reaches kunmap_local_indexed(), emits a warning, and hangs. The referenced stable-kernel changes limit the operation in this configuration. The bundle does not clearly establish every vulnerable-to-fixed version boundary.
Likely exposure
Prioritize 32-bit x86 Linux systems using high memory, CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP, and huge-page-backed tmpfs. The bundle identifies Linux 6.6, 6.6.60, 6.11.7, and 6.12 as affected entries, but its version data is insufficient to infer complete distribution-specific exposure.
Exploitation context
The documented trigger is a local file-write workload under an unusual kernel configuration. The CVSS vector requires local access with low privileges and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a publicly weaponized exploit.
Researcher notes
The source describes a warning at kunmap_local_indexed() followed by an interruptible hang during generic_perform_write() and shmem_file_write_iter(). It does not explain how the CVSS confidentiality and integrity impacts arise, provide a CWE, or document exploitation. Researchers should distinguish the demonstrated availability failure from broader impacts asserted only by the CVSS vector.
Mitigation direction
Identify systems running the listed Linux kernel versions and prioritize matching 32-bit high-memory configurations.
Obtain the appropriate fixed kernel package from the Linux distribution or system vendor.
Confirm the selected update incorporates the applicable referenced stable-kernel fix.
If updating is delayed, consult vendor guidance; the supplied sources name no temporary mitigation.
Reboot into the updated kernel according to normal change-control procedures.
Validation and detection
Record the running kernel version and architecture on potentially exposed systems.
Check whether CONFIG_DEBUG_KMAP_LOCAL_FORCE_MAP and high-memory support are enabled.
Determine whether affected systems use huge-page-backed tmpfs workloads.
Verify the installed kernel contains the applicable referenced stable fix.
After updating, confirm systems are running the intended kernel and monitor for related highmem warnings or hangs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-50222 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.