CVE-2026-43050

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

HIGH
7
CVSS Score
Published: May 1, 2026 at 02:15 PM UTC
Updated: June 17, 2026 at 10:48 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7
Exploit prediction
EPSS 0.1%

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_dereference/rcu_read_unlock in send_to_lecd(), lec_handle_bridge() and lec_atm_send() to safely access lecd - Use rcu_assign_pointer() followed by synchronize_rcu() in lec_atm_close() to ensure all readers have completed before proceeding. This is safe since lec_atm_close() is called from vcc_release() which holds lock_sock(), a sleeping lock. - Remove the manual sk_receive_queue drain from lec_atm_close() since vcc_destroy_socket() already drains it after lec_atm_close() returns. v2: Switch from spinlock + sock_hold/put approach to RCU to properly fix the race. The v1 spinlock approach had two issues pointed out by Eric Dumazet: 1. priv->lecd was still accessed directly after releasing the lock instead of using a local copy. 2. The spinlock did not prevent packets being queued after lec_atm_close() drains sk_receive_queue since timer and workqueue paths bypass netif_stop_queue(). Note: Syzbot patch testing was attempted but the test VM terminated unexpectedly with "Connection to localhost closed by remote host", likely due to a QEMU AHCI emulation issue unrelated to this fix. Compile testing with "make W=1 net/atm/lec.o" passes cleanly.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2532.6.12 ≤ v < 5.15.2032.6.12 ≤ v < 6.1.1682.6.12 ≤ v < 6.12.812.6.12 ≤ v < 6.18.222.6.12 ≤ v < 6.19.122.6.12 ≤ v < 6.6.1342.6.12 ≤ v < 7.02.6.12.1 ≤ v < 5.10.2535.11 ≤ v < 5.15.2035.16 ≤ v < 6.1.1686.13 ≤ v < 6.18.226.19 ≤ v < 6.19.126.2 ≤ v < 6.6.1346.7 ≤ v < 6.12.811da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.122.6.12 rc22.6.12 rc32.6.12 rc42.6.12 rc57.0 rc17.0 rc27.0 rc37.0 rc4
Vendor states this is fixed in 317843d5355062020649124eb4a0d7acbcc3f53e (fixed)
Vendor states this is fixed in 3989740fa4978e1d2d51ecc62be1b01093e104ad (fixed)
Vendor states this is fixed in 3e8b25f32f2f35549d03d77da030a24a45bdef5b (fixed)
Vendor states this is fixed in 5fbbb1ff936d7ff9528d929c1549977e8123d8a8 (fixed)
Vendor states this is fixed in 750a33f417f3d196b86375f8d9f8938bacf130fe (fixed)
Vendor states this is fixed in 922814879542c2e397b0e9641fd36b8202a8e555 (fixed)
Vendor states this is fixed in abc10f85a3965ac14b9ed7ad3e67b35604a63aa3 (fixed)
Vendor states this is fixed in b256d055da47258e63f8b40965f276c5f23d229a (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.253 (unaffected)
Vendor states this is fixed in 5.15.203 (unaffected)
Vendor states this is fixed in 6.1.168 (unaffected)
Vendor states this is fixed in 6.12.81 (unaffected)
Vendor states this is fixed in 6.18.22 (unaffected)
Vendor states this is fixed in 6.19.12 (unaffected)
Vendor states this is fixed in 6.6.134 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card