CVE-2026-43029 Vulnerability Analysis & Exploit Details

CVE-2026-43029
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-43029 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-43029 Details

Status: Analyzed

Last updated: 🕡 08 May 2026, 18:33 UTC
Originally published on: 🕒 01 May 2026, 15:16 UTC

Time between publication and last update: 7 days

CVSS Release: version 3

CVSS3 Source

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

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-43029 Vulnerability Summary

CVE-2026-43029: In the Linux kernel, the following vulnerability has been resolved: mptcp: fix soft lockup in mptcp_recvmsg() syzbot reported a soft lockup in mptcp_recvmsg() [0]. When receiving data with MSG_PEEK | MSG_WAITALL flags, the skb is not removed from the sk_receive_queue. This causes sk_wait_data() to always find available data and never perform actual waiting, leading to a soft lockup. Fix this by adding a 'last' parameter to track the last peeked skb. This allows sk_wait_data() to make informed waiting decisions and prevent infinite loops when MSG_PEEK is used. [0]: watchdog: BUG: soft lockup - CPU#2 stuck for 156s! [server:1963] Modules linked in: CPU: 2 UID: 0 PID: 1963 Comm: server Not tainted 6.19.0-rc8 #61 PREEMPT(none) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 RIP: 0010:sk_wait_data+0x15/0x190 Code: 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 41 56 41 55 41 54 49 89 f4 55 48 89 d5 53 48 89 fb <48> 83 ec 30 65 48 8b 05 17 a4 6b 01 48 89 44 24 28 31 c0 65 48 8b RSP: 0018:ffffc90000603ca0 EFLAGS: 00000246 RAX: 0000000000000000 RBX: ffff888102bf0800 RCX: 0000000000000001 RDX: 0000000000000000 RSI: ffffc90000603d18 RDI: ffff888102bf0800 RBP: 0000000000000000 R08: 0000000000000002 R09: 0000000000000101 R10: 0000000000000000 R11: 0000000000000075 R12: ffffc90000603d18 R13: ffff888102bf0800 R14: ffff888102bf0800 R15: 0000000000000000 FS: 00007f6e38b8c4c0(0000) GS:ffff8881b877e000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055aa7bff1680 CR3: 0000000105cbe000 CR4: 00000000000006f0 Call Trace: <TASK> mptcp_recvmsg+0x547/0x8c0 net/mptcp/protocol.c:2329 inet_recvmsg+0x11f/0x130 net/ipv4/af_inet.c:891 sock_recvmsg+0x94/0xc0 net/socket.c:1100 __sys_recvfrom+0xb2/0x130 net/socket.c:2256 __x64_sys_recvfrom+0x1f/0x30 net/socket.c:2267 do_syscall_64+0x59/0x2d0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e arch/x86/entry/entry_64.S:131 RIP: 0033:0x7f6e386a4a1d Code: 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 8d 05 f1 de 2c 00 41 89 ca 8b 00 85 c0 75 20 45 31 c9 45 31 c0 b8 2d 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 6b f3 c3 66 0f 1f 84 00 00 00 00 00 41 56 41 RSP: 002b:00007ffc3c4bb078 EFLAGS: 00000246 ORIG_RAX: 000000000000002d RAX: ffffffffffffffda RBX: 000000000000861e RCX: 00007f6e386a4a1d RDX: 00000000000003ff RSI: 00007ffc3c4bb150 RDI: 0000000000000004 RBP: 00007ffc3c4bb570 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000103 R11: 0000000000000246 R12: 00005605dbc00be0 R13: 00007ffc3c4bb650 R14: 0000000000000000 R15: 0000000000000000 </TASK>

Assessing the Risk of CVE-2026-43029

Access Complexity Graph

The exploitability of CVE-2026-43029 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-2026-43029

With low attack complexity and no required privileges, CVE-2026-43029 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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

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

CVE-2026-43029 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:6.18.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.20:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.20:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.21:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.21:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.117:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.117:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.12.59:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.12.59:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.17.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.17.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-43029: 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-2026-8288 – A vulnerability was determined in Open5GS up to 2.7.7. This affects the function gsm_handle_pdu_session_modification_qos_flow_descriptions of the f...
  • CVE-2025-9973 – Due to not validating the organization context when executing adaptive authentication flows, the WSO2 Identity Server allows adaptive authenticatio...
  • CVE-2025-10470 – The Magic Link authentication flow accepts multiple invalid authentication requests without adequate rate limiting or resource control, leading to ...
  • CVE-2026-6956 – ATutor is vulnerable to Reflected XSS in /install/install.php endpoint. An attacker can provide a specially crafted URL that, when opened, results ...
  • CVE-2026-6909 – ATutor is vulnerable to Reflected XSS in /install/upgrade.php endpoint. An attacker can provide a specially crafted URL that, when opened, results ...