CVE-2026-43050

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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:

  • priv->lecd was still accessed directly after releasing the
lock instead of using a local copy.
  • 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 v3
7.0
EG Score
7.0(medium)
EPSS
2.1%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (8)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

atm: lec: fix use-after-free in sock_def_readable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b256d055da47258e63f8b40965f276c5f23d229a
generic

atm: lec: fix use-after-free in sock_def_readable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/abc10f85a3965ac14b9ed7ad3e67b35604a63aa3
generic

atm: lec: fix use-after-free in sock_def_readable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/922814879542c2e397b0e9641fd36b8202a8e555
generic

atm: lec: fix use-after-free in sock_def_readable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/750a33f417f3d196b86375f8d9f8938bacf130fe
generic

atm: lec: fix use-after-free in sock_def_readable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5fbbb1ff936d7ff9528d929c1549977e8123d8a8
generic

atm: lec: fix use-after-free in sock_def_readable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e8b25f32f2f35549d03d77da030a24a45bdef5b
generic

atm: lec: fix use-after-free in sock_def_readable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3989740fa4978e1d2d51ecc62be1b01093e104ad
generic

atm: lec: fix use-after-free in sock_def_readable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/317843d5355062020649124eb4a0d7acbcc3f53e

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-19 14:31 UTCEPSS rescore
  2. 2026-07-18 10:04 UTCEPSS rescore
  3. 2026-07-16 17:03 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 14:05 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 67 more
  1. 2026-06-19 19:25 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-17 17:53 UTCEPSS rescore
  5. 2026-06-15 17:49 UTCEPSS rescore
  6. 2026-06-14 20:15 UTCGHSA enrichment
  7. 2026-06-14 08:49 UTCGHSA enrichment
  8. 2026-06-13 23:00 UTCEPSS rescore
  9. 2026-06-12 23:12 UTCEPSS rescore
  10. 2026-06-12 23:12 UTCEPSS rescore
  11. 2026-06-12 02:15 UTCGHSA enrichment
  12. 2026-06-11 14:49 UTCGHSA enrichment
  13. 2026-06-11 14:00 UTCEPSS rescore
  14. 2026-06-11 03:22 UTCGHSA enrichment
  15. 2026-06-10 22:18 UTCEPSS rescore
  16. 2026-06-10 13:22 UTCEPSS rescore
  17. 2026-06-10 13:22 UTCEPSS rescore
  18. 2026-06-10 13:08 UTCGHSA enrichment
  19. 2026-06-10 01:41 UTCGHSA enrichment
  20. 2026-06-09 14:15 UTCGHSA enrichment
  21. 2026-06-09 02:49 UTCGHSA enrichment
  22. 2026-06-08 14:17 UTCEPSS rescore
  23. 2026-06-08 14:17 UTCEPSS rescore
  24. 2026-06-08 14:11 UTCGHSA enrichment
  25. 2026-06-08 02:45 UTCGHSA enrichment
  26. 2026-06-07 15:25 UTCEPSS rescore
  27. 2026-06-07 15:25 UTCEPSS rescore
  28. 2026-06-07 15:19 UTCGHSA enrichment
  29. 2026-06-07 03:53 UTCGHSA enrichment
  30. 2026-06-06 16:26 UTCGHSA enrichment
  31. 2026-06-06 13:47 UTCEPSS rescore
  32. 2026-06-06 13:47 UTCEPSS rescore
  33. 2026-06-06 05:00 UTCGHSA enrichment
  34. 2026-06-05 22:47 UTCEPSS rescore
  35. 2026-06-05 17:33 UTCGHSA enrichment
  36. 2026-06-05 06:07 UTCGHSA enrichment
  37. 2026-06-04 18:40 UTCGHSA enrichment
  38. 2026-06-04 13:12 UTCEPSS rescore
  39. 2026-06-04 13:12 UTCEPSS rescore
  40. 2026-06-04 07:13 UTCGHSA enrichment
  41. 2026-06-03 19:38 UTCGHSA enrichment
  42. 2026-06-03 08:11 UTCGHSA enrichment
  43. 2026-06-02 20:44 UTCGHSA enrichment
  44. 2026-06-02 20:13 UTCEPSS rescore
  45. 2026-06-02 09:16 UTCGHSA enrichment
  46. 2026-06-01 21:50 UTCGHSA enrichment
  47. 2026-06-01 13:52 UTCEPSS rescore
  48. 2026-06-01 13:52 UTCEPSS rescore
  49. 2026-06-01 10:20 UTCGHSA enrichment
  50. 2026-05-31 22:30 UTCEPSS rescore
  51. 2026-05-31 22:30 UTCEPSS rescore
  52. 2026-05-31 00:16 UTCEPSS rescore
  53. 2026-05-31 00:16 UTCEPSS rescore
  54. 2026-05-29 13:44 UTCEPSS rescore
  55. 2026-05-29 13:44 UTCEPSS rescore
  56. 2026-05-28 13:44 UTCEPSS rescore
  57. 2026-05-28 13:44 UTCEPSS rescore
  58. 2026-05-27 13:40 UTCEPSS rescore
  59. 2026-05-27 13:40 UTCEPSS rescore
  60. 2026-05-26 13:44 UTCEPSS rescore
  61. 2026-05-26 07:18 UTCEPSS rescore
  62. 2026-05-20 22:38 UTCEPSS rescore
  63. 2026-05-20 22:38 UTCEPSS rescore
  64. 2026-05-20 14:50 UTCEG score recompute
  65. 2026-05-20 14:50 UTCGHSA enrichment
  66. 2026-05-20 11:22 UTCEPSS rescore
  67. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43050?
CVE-2026-43050 is a high vulnerability published on May 1, 2026. 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…
When was CVE-2026-43050 disclosed?
CVE-2026-43050 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43050 actively exploited?
CVE-2026-43050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43050?
CVE-2026-43050 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-43050?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43050, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43050

Explore →

Is Your Infrastructure Affected by CVE-2026-43050?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.