CVE-2026-45259
EUVD-2026-3996327.06.2026, 09:16
sigqueue(2) was marked as permitted in capability mode with the introduction of Capsicum in 2011, but the implementation of kern_sigqueue did not include a capability mode check restricting signal delivery to the calling process's own PID. A process in capability mode can use sigqueue(2) to send signals to any process it could signal following standard Unix permissions, bypassing the Capsicum sandbox restriction. A compromised sandboxed process could interfere with other processes, for example by sending SIGKILL or SIGSTOP. This could be any process running as the same user, or any process, for a superuser sandboxed process.Enginsight
Affected Products (NVD)
| Vendor | Product | Version |
|---|---|---|
| freebsd | freebsd | 14.3 |
| freebsd | freebsd | 14.3:p1 |
| freebsd | freebsd | 14.3:p10 |
| freebsd | freebsd | 14.3:p11 |
| freebsd | freebsd | 14.3:p12 |
| freebsd | freebsd | 14.3:p13 |
| freebsd | freebsd | 14.3:p14 |
| freebsd | freebsd | 14.3:p2 |
| freebsd | freebsd | 14.3:p3 |
| freebsd | freebsd | 14.3:p4 |
| freebsd | freebsd | 14.3:p5 |
| freebsd | freebsd | 14.3:p6 |
| freebsd | freebsd | 14.3:p7 |
| freebsd | freebsd | 14.3:p8 |
| freebsd | freebsd | 14.3:p9 |
| freebsd | freebsd | 14.4 |
| freebsd | freebsd | 14.4:p1 |
| freebsd | freebsd | 14.4:p2 |
| freebsd | freebsd | 14.4:p3 |
| freebsd | freebsd | 14.4:p4 |
| freebsd | freebsd | 14.4:p5 |
| freebsd | freebsd | 15.0 |
| freebsd | freebsd | 15.0:p1 |
| freebsd | freebsd | 15.0:p2 |
| freebsd | freebsd | 15.0:p3 |
| freebsd | freebsd | 15.0:p4 |
| freebsd | freebsd | 15.0:p5 |
| freebsd | freebsd | 15.0:p6 |
| freebsd | freebsd | 15.0:p7 |
| freebsd | freebsd | 15.0:p8 |
| freebsd | freebsd | 15.0:p9 |
𝑥
= Vulnerable software versions
Common Weakness Enumeration
Vulnerability Media Exposure