CVE-2026-45251

HIGH
Published May 21, 2026 Modified May 21, 2026 CWE-416

Description

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.

CVSS v3.1 Score

7.8
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS — Exploit Prediction

0.0014
Probability of exploitation
0.04%
Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-416 Use After Free

Affected Products

Vendor Product
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd
freebsd freebsd

References

Frequently Asked Questions

What is 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. It has a CVSS v3.1 base score of 7.8 (HIGH).
How severe is CVE-2026-45251? +
CVE-2026-45251 has a CVSS v3.1 score of 7.8 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching. The EPSS score is 0.0014, placing it in the 0th percentile for exploitation probability.
What products are affected by CVE-2026-45251? +
CVE-2026-45251 affects products from freebsd, specifically: freebsd. Check the affected products table above for specific version ranges.
How do I check if I'm vulnerable to CVE-2026-45251? +
You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

Don't wait for an exploit

Scan your website for vulnerabilities like CVE-2026-45251 — free, no signup required.

Start Free Scan