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

Published May 1, 2026
·
Updated

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

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

A race condition exists between lecatmclose() setting priv->lecd to NULL and concurrent access to priv->lecd in sendtolecd(), lechandlebridge(), and lecatmsend(). When the socket is freed via RCU while another thread is still using it, a use-after-free occurs in sockdefreadable() when accessing the socket's wait queue.

The root cause is that lecatmclose() 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 rcuassignpointer() in lecatmclose() and lecdattach() for safe pointer assignment - Use rcuaccesspointer() for NULL checks that do not dereference the pointer in lecstartxmit(), lecpush(), sendtolecd() and lecdattach() - Use rcureadlock/rcudereference/rcureadunlock in sendtolecd(), lechandlebridge() and lecatmsend() to safely access lecd - Use rcuassignpointer() followed by synchronizercu() in lecatmclose() to ensure all readers have completed before proceeding. This is safe since lecatmclose() is called from vccrelease() which holds locksock(), a sleeping lock. - Remove the manual skreceivequeue drain from lecatmclose() since vccdestroysocket() already drains it after lecatmclose() returns.

v2: Switch from spinlock + sockhold/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 lecatmclose() drains skreceivequeue since timer and workqueue paths bypass netifstopqueue().

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 Software

18 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=2.6.12.1<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.134
Linux Linux kernel>=6.7<6.12.81
Linux Linux kernel>=6.13<6.18.22
Linux Linux kernel>=6.19<6.19.12
Linux Linux kernel=2.6.12
Linux Linux kernel=2.6.12-rc2
Linux Linux kernel=2.6.12-rc3
Linux Linux kernel=2.6.12-rc4
Linux Linux kernel=2.6.12-rc5
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  2. Configuration

    Mark priv->lecd as __rcu in lec.h; use rcu_assign_pointer() for assignments in lec_atm_close() and lecd_attach(); use rcu_access_pointer() for non-dereferencing NULL checks in lec_start_xmit(), lec_push(), send_to_lecd(), and lecd_attach(); use rcu_read_lock(), rcu_dereference(), and rcu_read_unlock() when accessing lecd in send_to_lecd(), lec_handle_bridge(), and lec_atm_send(); in lec_atm_close(), use rcu_assign_pointer() followed by synchronize_rcu() before proceeding.

    Linux kernel ATM LEC priv->lecd = RCU-protected pointer (__rcu)
  3. Configuration

    Remove the manual sk_receive_queue drain from lec_atm_close(), since vcc_destroy_socket() drains it after lec_atm_close() returns.

    Linux kernel ATM LEC manual sk_receive_queue drain in lec_atm_close() = removed

Event History

May 1, 2026
CVE Published
via MITRE·02:15 PM
Data Sourced
via MITRE·02:15 PM
Description
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-43050?

CVE-2026-43050 is classified as a medium severity vulnerability due to its potential to cause a use-after-free condition.

2

How do I fix CVE-2026-43050?

To fix CVE-2026-43050, update the Linux kernel to the latest version where the vulnerability has been patched.

3

What systems are affected by CVE-2026-43050?

CVE-2026-43050 affects the Linux kernel, specifically those using the ATM LEC protocol.

4

What does CVE-2026-43050 exploit involve?

CVE-2026-43050 involves a race condition that can lead to a use-after-free vulnerability in the sock_def_readable function.

5

Has CVE-2026-43050 been resolved?

Yes, CVE-2026-43050 has been resolved in newer versions of the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203