Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2024-50220— fork: do not invoke uffd on fork if error occurs

EPSS 0.01% · P3
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2024-50220

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
fork: do not invoke uffd on fork if error occurs
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: fork: do not invoke uffd on fork if error occurs Patch series "fork: do not expose incomplete mm on fork". During fork we may place the virtual memory address space into an inconsistent state before the fork operation is complete. In addition, we may encounter an error during the fork operation that indicates that the virtual memory address space is invalidated. As a result, we should not be exposing it in any way to external machinery that might interact with the mm or VMAs, machinery that is not designed to deal with incomplete state. We specifically update the fork logic to defer khugepaged and ksm to the end of the operation and only to be invoked if no error arose, and disallow uffd from observing fork events should an error have occurred. This patch (of 2): Currently on fork we expose the virtual address space of a process to userland unconditionally if uffd is registered in VMAs, regardless of whether an error arose in the fork. This is performed in dup_userfaultfd_complete() which is invoked unconditionally, and performs two duties - invoking registered handlers for the UFFD_EVENT_FORK event via dup_fctx(), and clearing down userfaultfd_fork_ctx objects established in dup_userfaultfd(). This is problematic, because the virtual address space may not yet be correctly initialised if an error arose. The change in commit d24062914837 ("fork: use __mt_dup() to duplicate maple tree in dup_mmap()") makes this more pertinent as we may be in a state where entries in the maple tree are not yet consistent. We address this by, on fork error, ensuring that we roll back state that we would otherwise expect to clean up through the event being handled by userland and perform the memory freeing duty otherwise performed by dup_userfaultfd_complete(). We do this by implementing a new function, dup_userfaultfd_fail(), which performs the same loop, only decrementing reference counts. Note that we perform mmgrab() on the parent and child mm's, however userfaultfd_ctx_put() will mmdrop() this once the reference count drops to zero, so we will avoid memory leaks correctly here.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于存在错误发生时uffd调用问题。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux d2406291483775ecddaee929231a39c70c08fda2 ~ 92b472945dbf8abc020e9259c0088026f7027dfc -
LinuxLinux 6.8 -

II. Public POCs for CVE-2024-50220

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-50220

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-11-09 · 49 CVEs total

CVE-2024-50249ACPI: CPPC: Make rmw_lock a raw_spin_lock
CVE-2024-50252mlxsw: spectrum_ipip: Fix memory leak when changing remote IPv6 address
CVE-2024-50254bpf: Free dynamically allocated bits in bpf_iter_bits_destroy()
CVE-2024-50258net: fix crash when config small gso_max_size/gso_ipv4_max_size
CVE-2024-50259netdevsim: Add trailing zero to terminate the string in nsim_nexthop_bucket_activity_write
CVE-2024-50260sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
CVE-2024-50261macsec: Fix use-after-free while sending the offloading packet
CVE-2024-50262bpf: Fix out-of-bounds write in trie_get_next_key()
CVE-2024-50257netfilter: Fix use-after-free in get_info()
CVE-2024-50250fsdax: dax_unshare_iter needs to copy entire blocks
CVE-2024-50251netfilter: nft_payload: sanitize offset and length before calling skb_checksum()
CVE-2024-50248ntfs3: Add bounds checking to mi_enum_attr()
CVE-2024-50247fs/ntfs3: Check if more than chunk-size bytes are written
CVE-2024-50246fs/ntfs3: Add rough attr alloc_size check
CVE-2024-50244fs/ntfs3: Additional check in ni_clear()
CVE-2024-50245fs/ntfs3: Fix possible deadlock in mi_read
CVE-2024-50243fs/ntfs3: Fix general protection fault in run_is_mapped_full
CVE-2024-50242fs/ntfs3: Additional check in ntfs_file_release
CVE-2024-50241NFSD: Initialize struct nfsd4_copy earlier
CVE-2024-50240phy: qcom: qmp-usb: fix NULL-deref on runtime suspend

Showing top 20 of 49 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2024-50220

No comments yet


Leave a comment