Pinned Loading
-
Linux Kernel io_uring: OOB Read via ...
Linux Kernel io_uring: OOB Read via SQE_MIXED + sq_array Physical Index Bypass 1# Linux Kernel io_uring: Out-of-Bounds Read via SQE_MIXED + sq_array Physical Index Bypass23**CVE**: Pending (kernel fix and liburing test both merged)
4**Affected**: Linux kernels with `IORING_SETUP_SQE_MIXED` (introduced by commit [1cba30bf9fdd](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1cba30bf9fdd))
5**Fix**: [c76e0f1d77f8](https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git/commit/?id=c76e0f1d77f87e258193c2628253782d5ff414c7) — merged into `io_uring-7.0` on 2026-03-10
-
V8 Maglev JIT: Uninitialized Specula...
V8 Maglev JIT: Uninitialized SpeculationMode in SaveCallSpeculationScope (CL 7651434) 1// PoC: Uninitialized SpeculationMode in SaveCallSpeculationScope2//3// Triggers uninitialized read of saved_mode_ in the destructor of4// MaglevGraphBuilder::SaveCallSpeculationScope during Maglev JIT compilation.5// -
CVE-2026-47164 / GHSA-6x5c-84vm-5j56...
CVE-2026-47164 / GHSA-6x5c-84vm-5j56 — Vaultwarden SSO existing-user binding bypasses IdP email_verified check (HIGH 7.7, fixed in 1.36.0). Independent-reporter writeup. 1# Vaultwarden SSO existing-user binding skips the IdP `email_verified` check (CVE-2026-47164)23**Advisory:** [GHSA-6x5c-84vm-5j56](https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-6x5c-84vm-5j56)
4**CVE:** CVE-2026-47164
5**Severity:** HIGH — CVSS 7.7 (`AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L`)
-
consciousness-research
consciousness-research PublicResearch papers and experiments on consciousness preservation, mind uploading, and functional continuity benchmarks.
Python 4
-
agx-research
agx-research PublicAGX user-client research toolkit for Apple Silicon M2/M3/M4. Dispatch map, DYLD interpose tracer, unentitled chain replicator, per-chip kext diff.
Objective-C 3
Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.
If the problem persists, check the GitHub status page or contact support.



