CVE-2026-43050

published 1 May 2026 · updated 13 Nov 2026

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

7.0HighCVSS 7.0EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.253, Kernel 5.15.203, Kernel 6.1.168 and 12 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=2.6.12.1 <5.10.253, >=5.11 <5.15.203, >=5.16 <6.1.168, >=6.13 <6.18.22, >=6.19 <6.19.12, >=6.2 <6.6.134, >=6.7 <6.12.81, =2.6.12, =7.0, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3989740fa4978e1d2d51ecc62be1b01093e104ad, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e8b25f32f2f35549d03d77da030a24a45bdef5b, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5fbbb1ff936d7ff9528d929c1549977e8123d8a8, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <750a33f417f3d196b86375f8d9f8938bacf130fe, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <922814879542c2e397b0e9641fd36b8202a8e555, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <abc10f85a3965ac14b9ed7ad3e67b35604a63aa3, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b256d055da47258e63f8b40965f276c5f23d229a, >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <317843d5355062020649124eb4a0d7acbcc3f53e5.10.253, 5.15.203, 6.1.168, 6.18.22, 6.19.12, 6.6.134, 6.12.81, 3989740fa4978e1d2d51ecc62be1b01093e104ad, 3e8b25f32f2f35549d03d77da030a24a45bdef5b, 5fbbb1ff936d7ff9528d929c1549977e8123d8a8, 750a33f417f3d196b86375f8d9f8938bacf130fe, 922814879542c2e397b0e9641fd36b8202a8e555, abc10f85a3965ac14b9ed7ad3e67b35604a63aa3, b256d055da47258e63f8b40965f276c5f23d229a, 317843d5355062020649124eb4a0d7acbcc3f53e
linux-kernel: Kernel>=2.6.12 <5.10.253, >=5.11.0 <5.15.203, >=5.16.0 <6.1.168, >=6.13.0 <6.18.22, >=6.19.0 <6.19.12, >=6.2.0 <6.6.134, >=6.7.0 <6.12.815.10.253, 5.15.203, 6.1.168, 6.18.22, 6.19.12, 6.6.134, 6.12.81

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-43050 severity on Zeptric[![CVE-2026-43050](https://zeptric.io/badge/cve/CVE-2026-43050.svg)](https://zeptric.io/cve/CVE-2026-43050)