Kernel crash via unsynchronized LEC socket teardown
Published May 1, 2026 · Updated May 1, 2026
Use-after-free in the Linux Kernel ATM LANE subsystem allows local users to crash the kernel through concurrent LEC socket teardown. lec_atm_close() clears priv->lecd without synchronization while send_to_lecd(), lec_handle_bridge(), and lec_atm_send() dereference the pointer, allowing sock_def_readable() to access a freed socket wait queue. Triggering the race requires low-privileged local access and concurrent teardown of an ATM LANE client socket; the demonstrated consequence is a kernel memory-safety fault and crash.
Summary
What happened
Use-after-free in the Linux Kernel ATM LANE subsystem allows local users to crash the kernel through concurrent LEC socket teardown. lec_atm_close() clears priv->lecd without synchronization while send_to_lecd(), lec_handle_bridge(), and lec_atm_send() dereference the pointer, allowing sock_def_readable() to access a freed socket wait queue. Triggering the race requires low-privileged local access and concurrent teardown of an ATM LANE client socket; the demonstrated consequence is a kernel memory-safety fault and crash.
The record
- CVE
- CVE-2026-43050
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <317843d5355062020649124eb4a0d7acbcc3f53e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3989740fa4978e1d2d51ecc62be1b01093e104ad
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3e8b25f32f2f35549d03d77da030a24a45bdef5b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5fbbb1ff936d7ff9528d929c1549977e8123d8a8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <750a33f417f3d196b86375f8d9f8938bacf130fe
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <922814879542c2e397b0e9641fd36b8202a8e555
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <abc10f85a3965ac14b9ed7ad3e67b35604a63aa3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b256d055da47258e63f8b40965f276c5f23d229a
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Syzkaller C reproducer for sock_def_readable use-after-freeproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo