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.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

A fix is available — apply it.

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)
EG Risk
36(Track)
EG Risk 36/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
linuxKernel @ 5.10.253osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1

Weakness Classification(1)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 18:23 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 14:46 UTCEPSS rescore
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-23 21:47 UTCEG score recompute
  17. 2026-08-23 21:47 UTCVendor advisory
  18. 2026-08-23 21:46 UTCGHSA enrichment
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-19 17:03 UTCEPSS rescore
  23. 2026-08-18 13:48 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 13:20 UTCEG score recompute
Show 75 more
  1. 2026-08-17 13:20 UTCVendor advisory
  2. 2026-08-17 13:20 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 05:15 UTCEG score recompute
  5. 2026-08-16 05:15 UTCVendor advisory
  6. 2026-08-16 05:15 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 15:10 UTCVendor advisory
  10. 2026-08-14 15:10 UTCGHSA enrichment
  11. 2026-08-14 03:44 UTCEG score recompute
  12. 2026-08-14 03:44 UTCVendor advisory
  13. 2026-08-14 03:44 UTCGHSA enrichment
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 04:50 UTCVendor advisory
  16. 2026-08-13 04:50 UTCGHSA enrichment
  17. 2026-08-12 17:23 UTCEG score recompute
  18. 2026-08-12 17:23 UTCVendor advisory
  19. 2026-08-12 17:23 UTCGHSA enrichment
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 16:15 UTCEG score recompute
  22. 2026-08-11 16:15 UTCVendor advisory
  23. 2026-08-11 16:15 UTCGHSA enrichment
  24. 2026-08-11 13:43 UTCEPSS rescore
  25. 2026-08-11 01:47 UTCEG score recompute
  26. 2026-08-11 01:47 UTCVendor advisory
  27. 2026-08-11 01:47 UTCGHSA enrichment
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-10 13:14 UTCVendor advisory
  30. 2026-08-10 13:14 UTCGHSA enrichment
  31. 2026-08-10 01:47 UTCVendor advisory
  32. 2026-08-10 01:47 UTCGHSA enrichment
  33. 2026-08-09 14:19 UTCEG score recompute
  34. 2026-08-09 14:19 UTCVendor advisory
  35. 2026-08-09 14:18 UTCGHSA enrichment
  36. 2026-08-09 13:46 UTCEPSS rescore
  37. 2026-08-09 02:52 UTCEG score recompute
  38. 2026-08-09 02:52 UTCVendor advisory
  39. 2026-08-09 02:52 UTCGHSA enrichment
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 11:11 UTCVendor advisory
  42. 2026-08-08 11:10 UTCGHSA enrichment
  43. 2026-08-07 23:42 UTCEG score recompute
  44. 2026-08-07 23:42 UTCVendor advisory
  45. 2026-08-07 23:42 UTCGHSA enrichment
  46. 2026-08-07 12:15 UTCVendor advisory
  47. 2026-08-07 12:15 UTCGHSA enrichment
  48. 2026-08-06 21:45 UTCEG score recompute
  49. 2026-08-06 21:45 UTCVendor advisory
  50. 2026-08-06 21:45 UTCGHSA enrichment
  51. 2026-08-06 13:46 UTCEPSS rescore
  52. 2026-08-06 10:12 UTCVendor advisory
  53. 2026-08-06 10:12 UTCGHSA enrichment
  54. 2026-08-05 22:35 UTCEG score recompute
  55. 2026-08-05 22:35 UTCVendor advisory
  56. 2026-08-05 22:35 UTCGHSA enrichment
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-04 10:38 UTCEPSS rescore
  60. 2026-08-03 20:17 UTCEG score recompute
  61. 2026-08-03 20:17 UTCVendor advisory
  62. 2026-08-03 20:17 UTCGHSA enrichment
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-02 17:04 UTCVendor advisory
  65. 2026-08-02 17:04 UTCGHSA enrichment
  66. 2026-08-02 05:37 UTCEG score recompute
  67. 2026-08-02 05:37 UTCVendor advisory
  68. 2026-08-02 05:37 UTCGHSA enrichment
  69. 2026-08-02 02:27 UTCEPSS rescore
  70. 2026-08-01 04:16 UTCEPSS rescore
  71. 2026-07-30 16:28 UTCEPSS rescore
  72. 2026-07-30 01:30 UTCEPSS rescore
  73. 2026-07-28 15:36 UTCEPSS rescore
  74. 2026-07-27 14:13 UTCEPSS rescore
  75. 2026-07-26 14:54 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 0% probability of exploitation in the next 30 days, which ranks it in the top 98.0% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.