CVE-2022-50323 Vulnerability Analysis & Exploit Details

CVE-2022-50323
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2022-50323 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-50323 Details

Status: Analyzed

Last updated: 🕒 04 Dec 2025, 15:07 UTC
Originally published on: 🕒 15 Sep 2025, 15:15 UTC

Time between publication and last update: 79 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2022-50323 Vulnerability Summary

CVE-2022-50323: In the Linux kernel, the following vulnerability has been resolved: net: do not sense pfmemalloc status in skb_append_pagefrags() skb_append_pagefrags() is used by af_unix and udp sendpage() implementation so far. In commit 326140063946 ("tcp: TX zerocopy should not sense pfmemalloc status") we explained why we should not sense pfmemalloc status for pages owned by user space. We should also use skb_fill_page_desc_noacc() in skb_append_pagefrags() to avoid following KCSAN report: BUG: KCSAN: data-race in lru_add_fn / skb_append_pagefrags write to 0xffffea00058fc1c8 of 8 bytes by task 17319 on cpu 0: __list_add include/linux/list.h:73 [inline] list_add include/linux/list.h:88 [inline] lruvec_add_folio include/linux/mm_inline.h:323 [inline] lru_add_fn+0x327/0x410 mm/swap.c:228 folio_batch_move_lru+0x1e1/0x2a0 mm/swap.c:246 lru_add_drain_cpu+0x73/0x250 mm/swap.c:669 lru_add_drain+0x21/0x60 mm/swap.c:773 free_pages_and_swap_cache+0x16/0x70 mm/swap_state.c:311 tlb_batch_pages_flush mm/mmu_gather.c:59 [inline] tlb_flush_mmu_free mm/mmu_gather.c:256 [inline] tlb_flush_mmu+0x5b2/0x640 mm/mmu_gather.c:263 tlb_finish_mmu+0x86/0x100 mm/mmu_gather.c:363 exit_mmap+0x190/0x4d0 mm/mmap.c:3098 __mmput+0x27/0x1b0 kernel/fork.c:1185 mmput+0x3d/0x50 kernel/fork.c:1207 copy_process+0x19fc/0x2100 kernel/fork.c:2518 kernel_clone+0x166/0x550 kernel/fork.c:2671 __do_sys_clone kernel/fork.c:2812 [inline] __se_sys_clone kernel/fork.c:2796 [inline] __x64_sys_clone+0xc3/0xf0 kernel/fork.c:2796 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd read to 0xffffea00058fc1c8 of 8 bytes by task 17325 on cpu 1: page_is_pfmemalloc include/linux/mm.h:1817 [inline] __skb_fill_page_desc include/linux/skbuff.h:2432 [inline] skb_fill_page_desc include/linux/skbuff.h:2453 [inline] skb_append_pagefrags+0x210/0x600 net/core/skbuff.c:3974 unix_stream_sendpage+0x45e/0x990 net/unix/af_unix.c:2338 kernel_sendpage+0x184/0x300 net/socket.c:3561 sock_sendpage+0x5a/0x70 net/socket.c:1054 pipe_to_sendpage+0x128/0x160 fs/splice.c:361 splice_from_pipe_feed fs/splice.c:415 [inline] __splice_from_pipe+0x222/0x4d0 fs/splice.c:559 splice_from_pipe fs/splice.c:594 [inline] generic_splice_sendpage+0x89/0xc0 fs/splice.c:743 do_splice_from fs/splice.c:764 [inline] direct_splice_actor+0x80/0xa0 fs/splice.c:931 splice_direct_to_actor+0x305/0x620 fs/splice.c:886 do_splice_direct+0xfb/0x180 fs/splice.c:974 do_sendfile+0x3bf/0x910 fs/read_write.c:1255 __do_sys_sendfile64 fs/read_write.c:1323 [inline] __se_sys_sendfile64 fs/read_write.c:1309 [inline] __x64_sys_sendfile64+0x10c/0x150 fs/read_write.c:1309 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd value changed: 0x0000000000000000 -> 0xffffea00058fc188 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 17325 Comm: syz-executor.0 Not tainted 6.1.0-rc1-syzkaller-00158-g440b7895c990-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022

Assessing the Risk of CVE-2022-50323

Access Complexity Graph

The exploitability of CVE-2022-50323 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-50323

CVE-2022-50323 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-50323, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-50323, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2022-50323 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2022-50323 poses no threat to data integrity.
  • Availability: High
    CVE-2022-50323 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2022-50323 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.15.68:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.68:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.69:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.69:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.70:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.70:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.71:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.71:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.72:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.72:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.73:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.73:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.74:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.74:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.75:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.75:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.76:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.76:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.19:rc8:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.19:rc8:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.0:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.0:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.1:rc2:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-50323: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-14298 – The FiboSearch – Ajax Search for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `thegem_te_search` ...
  • CVE-2025-12492 – The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerab...
  • CVE-2025-13619 – The Flex Store Users plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.1.0. This is due to the 'fs...
  • CVE-2025-12820 – The Pure WC Variation Swatches WordPress plugin through 1.1.7 does not have an authorization check when updating its settings, which could allow an...
  • CVE-2025-14735 – The "Amazon affiliate lite Plugin" plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and ...