HIGH
atm LecSocket UAF
CVE-2026-43050
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
KernelScan AI6.5MEDIUM
01Description
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.
02KernelScan AI Analysis
Risk summary
A race condition in the ATM LAN Emulation Client (LEC) subsystem allows local attackers with low privileges to trigger a use-after-free during socket teardown. The dangling pointer can be accessed from multiple code paths including send_to_lecd(), lec_handle_bridge(), and lec_atm_send(), leading to kernel memory corruption, potential information leak from freed heap slabs, and kernel panic.
Vulnerability analysis
The vulnerability stems from unsynchronized access to the priv->lecd pointer in the ATM LEC subsystem. lec_atm_close() clears the pointer without coordination while concurrent threads dereference it, creating a use-after-free when the ATM socket is freed via RCU. The fix converts priv->lecd to an RCU-protected pointer with proper read-side critical sections and synchronize_rcu() in the teardown path. Attack surface is limited to systems with ATM hardware or emulation configured. Because the freed socket is accessed for both reads (wait queue) and writes (skb_queue_tail, sk_data_ready function pointer dispatch), the bug provides both information-disclosure and memory-corruption primitives.
03Fix Versions
| Branch | Fixed in | Patch commit |
|---|---|---|
| 5.10 | 5.10.253 | 3e8b25f32f2f |
| 5.15 | 5.15.203 | 750a33f417f3 |
| 6.1 | 6.1.168 | 317843d53550 |
| 6.12 | 6.12.81 | 3989740fa497 |
| 6.18 | 6.18.22 | abc10f85a396 |
| 6.19 | 6.19.12 | 5fbbb1ff936d |
| 6.6 | 6.6.134 | b256d055da47 |
| mainline | 7.0 | 922814879542 |