Menu

Star on GitHub · 3.2k

CVE-2026-43050

7.0 · HIGH

In the Linux kernel, the following vulnerability has been resolved: atm: lec: fix use-after-free in sock_def_readable() A race condition exists between lec_atm_close() setting priv->lecd to NULL…

Published May 1, 2026CWE-416EPSS 0.16%

Overview

CVE-2026-43050 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.0 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

atm: lec: fix use-after-free in sock_def_readable()

A race condition exists between lec_atm_close() setting priv->lecd

to NULL and concurrent access to priv->lecd in send_to_lecd(),

lec_handle_bridge(), and lec_atm_send(). When the socket is freed

via RCU while another thread is still using it, a use-after-free

occurs in sock_def_readable() when accessing the socket's wait queue.

The root cause is that lec_atm_close() clears priv->lecd without

any synchronization, while callers dereference priv->lecd without

any protection against concurrent teardown.

Fix this by converting priv->lecd to an RCU-protected pointer:

- Mark priv->lecd as __rcu in lec.h

- Use rcu_assign_pointer() in lec_atm_close() and lecd_attach()

for safe pointer assignment

- Use rcu_access_pointer() for NULL checks that do not dereference

the pointer in lec_start_xmit(), lec_push(), send_to_lecd() and

lecd_attach()

- Use rcu_read_lock/rcu_dere

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-43050?

CVE-2026-43050 is a high-severity vulnerability. It was published on May 1, 2026 and has a CVSS 3.1 base score of 7.0 (HIGH).

How severe is CVE-2026-43050?

This vulnerability has a CVSS 3.1 base score of 7.0, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-43050?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-43050?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-43050 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all