7

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

Analyzed
AliasesUBUNTU-CVE-2026-43050DEBIAN-CVE-2026-43050
Published 01-05-2026Last modified 11-05-2026

Vulnerability summary

CVE-2026-43050 is a high (CVSS 7.0) Use After Free vulnerability in linux. EPSS estimates a 0.12% chance of exploitation in the next 30 days, higher than 1.7% of scored vulnerabilities.

Priority
Routine

Not severe (CVSS 7, local access); no exploitation reported by the 5 checked sources

Source freshness unavailable

How is this decided?
CVSS score
7.0/10
010
High · v3.1 (NVD)
EPSS score
0.12%
0%100%
Low · -0.04 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 32 · Related 30

Timeline

  1. 01-05-2026
    PublishedVulnerability first disclosed.
  2. 11-05-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.12%

Chance of exploitation in the next 30 days

Percentile

2%

Versus all other CVEs

30-day change

Decrease -0.04 pp

From 0.16% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.

Ubuntu157 products
  • linuxAll versions (No fix recorded) | < 5.15.0-186.196 | < 6.8.0-136.136
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 5.15.0-1112.119 | < 6.8.0-1061.64
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Linux2 products
  • linux≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 3e8b25f32f2f35549d03d77da030a24a45bdef5b | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 750a33f417f3d196b86375f8d9f8938bacf130fe | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 317843d5355062020649124eb4a0d7acbcc3f53e | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < b256d055da47258e63f8b40965f276c5f23d229a | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 3989740fa4978e1d2d51ecc62be1b01093e104ad | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < abc10f85a3965ac14b9ed7ad3e67b35604a63aa3 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 5fbbb1ff936d7ff9528d929c1549977e8123d8a8 | ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 922814879542c2e397b0e9641fd36b8202a8e555 | 2.6.12
  • linux_kernel≥ 2.6.12.1, < 5.10.253 | ≥ 5.11, < 5.15.203 | ≥ 5.16, < 6.1.168 | ≥ 6.2, < 6.6.134 | ≥ 6.7, < 6.12.81 | ≥ 6.13, < 6.18.22 | ≥ 6.19, < 6.19.12 | 2.6.12 | 2.6.12:rc2 | 2.6.12:rc3 | 2.6.12:rc4 | 2.6.12:rc5 | 7.0:rc1 | 7.0:rc2 | 7.0:rc3 | 7.0:rc4
Debian1 product
  • linux< 6.1.170-1 | < 6.12.85-1 | < 6.19.12-1

3 vendors · 160 products

References

39 links
Show all 39 references