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.
References
| Link | Resource |
|---|---|
| https://security.freebsd.org/advisories/FreeBSD-SA-26:28.capsicum.asc | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-06-27 09:16
Updated : 2026-07-01 14:04
NVD link : CVE-2026-45259
Mitre link : CVE-2026-45259
CVE.ORG link : CVE-2026-45259
JSON object : View
Products Affected
freebsd
- freebsd
CWE
CWE-266
Incorrect Privilege Assignment
