Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

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.


Security Impact Summary

This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.8, requiring local system access to exploit with relatively low complexity without requiring user interaction requiring only low-level privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from freebsd organizations running these solutions should prioritize assessment and patching.

Historical Context

Reported in 2026, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.


Published

2026-05-21T10:16:26.043

Last Modified

2026-05-21T19:01:22.710

Status

Analyzed

Source

[email protected]

Severity

CVSSv3.1: 7.8 (HIGH)

Weaknesses
  • Type: Secondary
    CWE-416

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.3 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 14.4 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes
Operating System freebsd freebsd 15.0 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For freebsd's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.