在将 knote 从父 kqueue 复制到子 kqueue 时,复制代码在将 knote 标记为“in-flux”并释放 kqueue 锁之前,未能正确排除用作内部跟踪列表遍历位置的标记 knote。如果在释放锁后另一个线程释放了某个标记 knote,则后续的 in-flux 减量操作将在已释放的内存上进行。 未经特权的本地用户可能利用这些竞争条件来提升权限。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-58098 | Heap out-of-bounds access in semop(2) | |
| CVE-2026-58100 | Memory safety bugs in kqueue copy-on-fork implementation | |
| CVE-2026-101302 | Remote DoS via receive-side kernel TLS | |
| CVE-2026-101306 | Multiple jail filesystem root escapes | |
| CVE-2026-101305 | Multiple jail filesystem root escapes | |
| CVE-2026-101304 | Multiple jail filesystem root escapes | |
| CVE-2026-101303 | IPv6 UDP sendto(2) bypasses jail loopback restriction | |
| CVE-2026-101307 | Remotely triggerable buffer overflow in tcp_rack | |
| CVE-2026-101308 | TOCTOU race between sound(4) buffer resizing and mmap | |
| CVE-2026-101311 | Multiple vulnerabilities in bhyve device models | |
| CVE-2026-101309 | Multiple vulnerabilities in bhyve device models | |
| CVE-2026-101310 | Multiple vulnerabilities in bhyve device models |
No comments yet