CVE record
CVE-2026-45251
A file descriptor can be closed while a thread is blocked in a poll(2) or select(2) call waiting for that descriptor. Because the blocked thread does not hold a reference to the underlying object, this closure may result in the object being freed while the thread remains blocked. In this situation, the kernel must remove the blocked thread from the per-object wait queue prior to freeing the object. In the case of some file descriptor types, the kernel failed to unlink blocked threads from the object before freeing it. When the blocked thread is subsequently woken, it accesses memory that has already been freed resulting in a use-after-free vulnerability. The use-after-free vulnerability may be triggered by an unprivileged local user and can be exploited to obtain superuser privileges.
Amazon picks for vulnerability response
Product discovery links are localized to Amazon US when country data is available.
This page may contain affiliate links. We may earn a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases.
Hardware security keys
Physical MFA keys for admin accounts, cloud consoles, password managers, and incident response workflows.
Security engineering books
Books on secure design, incident response, threat modeling, cloud security, and practical defense.
Ethernet cable testers
Portable testers for validating office, rack, home lab, and troubleshooting cable runs.
Vulnerability metadata
- Published
- 2026-05-21T04:46:26.043Z
- Modified
- 2026-05-21T13:31:22.710Z
- EPSS
- Not available
- Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Recommended platforms
Affiliate-supported recommendations for CVE-2026-45251 vulnerability response.
This page may contain affiliate links. We may earn a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases.
Security engineering books
Browse practical security, incident response, cloud security, and secure coding books for team learning.
Cloud security platform
Continuously review cloud posture, exposed services, identity risks, and misconfigurations.
Monitoring and incident response
Track uptime, logs, traces, TLS expiry, API latency, and production security signals.