125 matches found
AceLdr
AceLdr - Avoid Memory Scanners A position-independent reflective loader for Cobalt Strike. Zero results from Hunt-Sleeping-Beacons, BeaconHunter, BeaconEye, Patriot, Moneta, PE-sieve, or MalMemDetect. Features Easy to Use Import a single CNA script before generating shellcode. Dynamic Memory...
memguard
MemGuard Enclave de software para almacenar información sensible en memoria. Este paquete intenta reducir la probabilidad de que datos sensibles queden expuestos mientras están en memoria. Su objetivo es ser compatible con los principales sistemas operativos y está escrito en Go puro...
patriot
Patriot Small research project for detecting various kinds of in-memory stealth techniques. Download the latest release here. The current version supports the following detections: Suspicious CONTEXT structures pointing to VirtualProtect functions. Targets research by Austin Hudson Foliage and Ek...
SleepyCrypt
SleepyCrypt A shellcode function to encrypt a running process image in memory when sleeping. This is the companion code for my blog post here. Build Just run build.sh to compile the C code, extract the .text section as shellcode, and compile it into a test binary called sleep.exe. This will requi...
NimShellcodeFluctuation
NimShellcodeFluctuation Nim Port of the original repo: https://github.com/mgeeky/ShellcodeFluctuation All comments were copy pasted as they were from the original Repository as they really helped me to understand the technique. For more information about the technique itself I highly recommend...
CVE-2026-4932
IBM PowerVM Hypervisor vulnerability CVE-2026-4932 affects FW1110.00–FW1110.20 and FW1060.00–FW1060.71. Affects PowerVM Hypervisor and TME hardware; attacker with physical access to Transparent Memory Encryption could decrypt memory due to insufficient cryptographic entropy. Impact is high confid...
Security Bulletin: This Power System update is being released to address CVE-2026-4932
Summary A firmware issue was identified where the generated AES key used to initialize the Transparent Memory Encryption TME hardware has weakened encryption strength. Vulnerability Details CVEID:CVE-2026-4932 DESCRIPTION: PowerVM Hypervisor could allow an attacker with physical access to the...
SUSE CVE-2026-64104
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When setmemoryencrypted,decrypted fail, the user cannot know at which point the function failed, meaning that the pages are left in an unknown state from the point of view o...
CVE-2026-64104
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When setmemoryencrypted,decrypted fail, the user cannot know at which point the function failed, meaning that the pages are left in an unknown state from the point of view o...
CVE-2026-64104 virt: sev-guest: Explicitly leak pages in unknown state
In the Linux kernel, the following vulnerability has been resolved: virt: sev-guest: Explicitly leak pages in unknown state When setmemoryencrypted,decrypted fail, the user cannot know at which point the function failed, meaning that the pages are left in an unknown state from the point of view o...
CVE-2026-64104
CVE-2026-64104 (Linux kernel) affects virt: sev-guest where set_memory_encrypted()/set_memory_decrypted() can fail leaving pages in an unknown state, potentially unencrypted and not safely returnable to the buddy allocator. The provided documentation notes that to avoid this, the pages should not...
PT-2026-61421
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the sev-guest component of the virt subsystem. When the set memory encrypted or set memory decrypted functions fail, the caller cannot determine the exact point of...
Astra Linux – Vulnerability in Linux 6.1
In the Linux kernel, the following vulnerability has been resolved: arm64/fpsimd: Signal: Fix for restoring SVE context When SME is supported, restoring the SVE signal context can fail in several ways. This can result in the task being placed in an invalid state, where the kernel might read from...
Linux Distros Unpatched Vulnerability : CVE-2026-31592
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - KVM: SEV: Protect all of sevmemencregisterregion with kvm-lock Take and hold kvm-lock for before checking sevguest in sevmemencregisterregion, as sevguest isn't...
KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION
...
SUSE CVE-2026-31590
In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Drop WARN on large size for KVMMEMORYENCRYPTREGREGION Drop the WARN in sevpinmemory on npages overflowing an int, as the WARN is comically trivially to trigger from userspace, e.g. by doing: struct kvmencregion range =...
CVE-2026-31593
In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU Reject synchronizing vCPU state to its associated VMSA if the vCPU has already been launched, i.e. if the VMSA has already been encrypted. On a host wit...
CVE-2026-31593 KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU
In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU Reject synchronizing vCPU state to its associated VMSA if the vCPU has already been launched, i.e. if the VMSA has already been encrypted. On a host wit...
CVE-2026-31593
CVE-2026-31593 is a Linux kernel KVM SEV SNP issue. The vulnerability arises when updating an already-launched and encrypted vCPU state: attempting to sync the vCPU's VMSA can trigger an SEV-SNP cryptographic memory protection (RMP) violation, causing a host panic/DoS. Technical details across mu...
CVE-2026-31592 KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm->lock
In the Linux kernel, the following vulnerability has been resolved: KVM: SEV: Protect all of sevmemencregisterregion with kvm-lock Take and hold kvm-lock for before checking sevguest in sevmemencregisterregion, as sevguest isn't stable unless kvm-lock is held or KVM can guarantee KVMSEVINIT2 has...