801 matches found
EUVD-2026-71418
In the Linux kernel, the following vulnerability has been resolved: futex: Fix race on the initial mm-futex.phash.ref allocation futexhashallocate allocates mm-futex.phash.ref without any locking. Commit d9b05321e21e "futex: Move futexhashfree back to mmput" moved the allocation here and assumed...
CVE-2026-80775 futex: Fix race on the initial mm->futex.phash.ref allocation
In the Linux kernel, the following vulnerability has been resolved: futex: Fix race on the initial mm-futex.phash.ref allocation futexhashallocate allocates mm-futex.phash.ref without any locking. Commit d9b05321e21e "futex: Move futexhashfree back to mmput" moved the allocation here and assumed...
CVE-2026-80775
In the Linux kernel, the following vulnerability has been resolved: futex: Fix race on the initial mm-futex.phash.ref allocation futexhashallocate allocates mm-futex.phash.ref without any locking. Commit d9b05321e21e "futex: Move futexhashfree back to mmput" moved the allocation here and assumed...
CVE-2026-80775
CVE-2026-80775 is a race condition in the Linux kernel futex subsystem, specifically in the initial allocation of mm->futex.phash.ref. The root cause is a concurrent execution scenario introduced by nested vfork : when a vfork child calls vfork again and is killed with SIGKILL, the parent and ...
CVE-2026-80758
CVE-2026-80758 is a use-after-free vulnerability in the Linux kernel's futex subsystem. The flaw is in futex_private_hash_put(), which drops its reference to the private hash (fph) before evaluating fph->mm for wake_up_var(). Because futex_ref_put() re-enables preemption before returning, a ta...
EUVD-2026-71401
In the Linux kernel, the following vulnerability has been resolved: futex: Avoid private hash use-after-free on final put futexprivatehashput drops the reference to fph before evaluating fph-mm for wakeupvar. futexrefput enables preemption again before returning. If that put drops the final...
CVE-2026-80758
In the Linux kernel, the following vulnerability has been resolved: futex: Avoid private hash use-after-free on final put futexprivatehashput drops the reference to fph before evaluating fph-mm for wakeupvar. futexrefput enables preemption again before returning. If that put drops the final...
CVE-2026-80758 futex: Avoid private hash use-after-free on final put
In the Linux kernel, the following vulnerability has been resolved: futex: Avoid private hash use-after-free on final put futexprivatehashput drops the reference to fph before evaluating fph-mm for wakeupvar. futexrefput enables preemption again before returning. If that put drops the final...
The vulnerability of the need_futex_hash_allocate_default() function in the kernel/fork.c module of the Linux operating system allows a attacker to compromise the confidentiality, integrity, and accessibility of the protected information.
The vulnerability of the needfutexhashallocatedefault function in the kernel/fork.c module of the Linux operating system is related to the use of memory after it is freed. Exploiting this vulnerability could allow an attacker to compromise the confidentiality, integrity, and accessibility of the...
Important: Red Hat Security Advisory: kpatch-patch-5_14_0-687_10_1 security update
An update for kpatch-patch-5140-687101 is now available for Red Hat Enterprise Linux 9. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System CVSS base score, which gives a detailed severity rating, is available for each...
kernel: futex: Drop CLONE_THREAD requirement for private default hash alloc
A flaw was found in the Linux kernel's futex subsystem. The needfutexhashallocatedefault function incorrectly relies on CLONETHREAD semantics, which can lead to non-concurrency issues when memory allocations mm-futexref pcpu allocations are shared across CLONEVM clones, excluding vfork. This can...
kernel: futex: Drop CLONE_THREAD requirement for private default hash alloc
A flaw was found in the Linux kernel's futex subsystem. The needfutexhashallocatedefault function incorrectly relies on CLONETHREAD semantics, which can lead to non-concurrency issues when memory allocations mm-futexref pcpu allocations are shared across CLONEVM clones, excluding vfork. This can...
Exploit for Use After Free in Linux Linux_Kernel
root-s24-e1s Per-boot local root on Samsung Galaxy S24 SM-S...
Exploit for Use After Free in Linux Linux_Kernel
GhostLock — PFEM10 CVE-2026-43499 IonStack exploit for OP...
Exploit for Use After Free in Linux Linux_Kernel
pixel-ksu-root An adb-driven tool that turns a stock, locked-...
The vulnerability of the SYSCALL_DEFINE4() function in the kernel/futex/syscalls.c module of the Linux operating system allows a attacker to compromise the confidentiality, integrity, and accessibility of the protected information.
The vulnerability of the SYSCALLDEFINE4 function in the kernel/futex/syscalls.c module of the Linux operating system is related to errors during the update of the reference counter. Exploiting this vulnerability can allow an attacker to compromise the confidentiality, integrity, and accessibility...
kernel: rtmutex: Use waiter::task instead of current in remove_waiter()
A flaw was found in the Linux kernel. When the kernel's real-time mutex rtmutex component performs a specific operation called 'proxy-lock rollback' during futex requeue, it incorrectly handles task pointers. This can lead to a 'Use-After-Free' UAF vulnerability, where the system attempts to use...
kernel: rtmutex: Use waiter::task instead of current in remove_waiter()
A flaw was found in the Linux kernel. When the kernel's real-time mutex rtmutex component performs a specific operation called 'proxy-lock rollback' during futex requeue, it incorrectly handles task pointers. This can lead to a 'Use-After-Free' UAF vulnerability, where the system attempts to use...
kernel: rtmutex: Use waiter::task instead of current in remove_waiter()
A flaw was found in the Linux kernel. When the kernel's real-time mutex rtmutex component performs a specific operation called 'proxy-lock rollback' during futex requeue, it incorrectly handles task pointers. This can lead to a 'Use-After-Free' UAF vulnerability, where the system attempts to use...
kernel: rtmutex: Use waiter::task instead of current in remove_waiter()
A flaw was found in the Linux kernel. When the kernel's real-time mutex rtmutex component performs a specific operation called 'proxy-lock rollback' during futex requeue, it incorrectly handles task pointers. This can lead to a 'Use-After-Free' UAF vulnerability, where the system attempts to use...