CVE-2021-47590 Vulnerability Analysis & Exploit Details

CVE-2021-47590
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2021-47590 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-2021-47590 Details

Status: Analyzed

Last updated: 🕓 27 Aug 2024, 16:14 UTC
Originally published on: 🕒 19 Jun 2024, 15:15 UTC

Time between publication and last update: 69 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-2021-47590 Vulnerability Summary

CVE-2021-47590: In the Linux kernel, the following vulnerability has been resolved: mptcp: fix deadlock in __mptcp_push_pending() __mptcp_push_pending() may call mptcp_flush_join_list() with subflow socket lock held. If such call hits mptcp_sockopt_sync_all() then subsequently __mptcp_sockopt_sync() could try to lock the subflow socket for itself, causing a deadlock. sysrq: Show Blocked State task:ss-server state:D stack: 0 pid: 938 ppid: 1 flags:0x00000000 Call Trace: <TASK> __schedule+0x2d6/0x10c0 ? __mod_memcg_state+0x4d/0x70 ? csum_partial+0xd/0x20 ? _raw_spin_lock_irqsave+0x26/0x50 schedule+0x4e/0xc0 __lock_sock+0x69/0x90 ? do_wait_intr_irq+0xa0/0xa0 __lock_sock_fast+0x35/0x50 mptcp_sockopt_sync_all+0x38/0xc0 __mptcp_push_pending+0x105/0x200 mptcp_sendmsg+0x466/0x490 sock_sendmsg+0x57/0x60 __sys_sendto+0xf0/0x160 ? do_wait_intr_irq+0xa0/0xa0 ? fpregs_restore_userregs+0x12/0xd0 __x64_sys_sendto+0x20/0x30 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f9ba546c2d0 RSP: 002b:00007ffdc3b762d8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 00007f9ba56c8060 RCX: 00007f9ba546c2d0 RDX: 000000000000077a RSI: 0000000000e5e180 RDI: 0000000000000234 RBP: 0000000000cc57f0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f9ba56c8060 R13: 0000000000b6ba60 R14: 0000000000cc7840 R15: 41d8685b1d7901b8 </TASK> Fix the issue by using __mptcp_flush_join_list() instead of plain mptcp_flush_join_list() inside __mptcp_push_pending(), as suggested by Florian. The sockopt sync will be deferred to the workqueue.

Assessing the Risk of CVE-2021-47590

Access Complexity Graph

The exploitability of CVE-2021-47590 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-2021-47590

CVE-2021-47590 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-2021-47590, 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-2021-47590, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

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

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.043% (probability of exploit)

EPSS Percentile: 12.0% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 88.0% of others.

CVE-2021-47590 References

External References

CWE Common Weakness Enumeration

CWE-667

CAPEC Common Attack Pattern Enumeration and Classification

  • Forced Deadlock CAPEC-25 The adversary triggers and exploits a deadlock condition in the target software to cause a denial of service. A deadlock can occur when two or more competing actions are waiting for each other to finish, and thus neither ever does. Deadlock conditions can be difficult to detect.
  • Leveraging Race Conditions CAPEC-26 The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
  • Leveraging Race Conditions via Symbolic Links CAPEC-27 This attack leverages the use of symbolic links (Symlinks) in order to write to sensitive files. An attacker can create a Symlink link to a target file not otherwise accessible to them. When the privileged program tries to create a temporary file with the same name as the Symlink link, it will actually write to the target file pointed to by the attackers' Symlink link. If the attacker can insert malicious content in the temporary file they will be writing to the sensitive file by using the Symlink. The race occurs because the system checks if the temporary file exists, then creates the file. The attacker would typically create the Symlink during the interval between the check and the creation of the temporary file.

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:5.13:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.0-52:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.0-52:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.13:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.13:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.20:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.20:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14.21:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14.21:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.14:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.14:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.0:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.0:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.0-58:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.0-58:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.3:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.3:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:5.15.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:5.15.10:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2021-47590: 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-3275 – The Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the TF E Slider widget in all versions up...
  • CVE-2025-1457 – The Element Pack Addons for Elementor – Free Templates and Widgets for Your WordPress Websites plugin for WordPress is vulnerable to Stored Cross-S...
  • CVE-2025-1093 – The AIHub theme for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the generate_image function in all ver...
  • CVE-2025-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...
  • CVE-2025-3278 – The UrbanGo Membership plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.4. This is due to the plugi...