Most recent entries from all

fkie_cve-2026-98260

In the Linux kernel, the following vulnerability has been resolved:

exec: Cleanup POSIX timers right after de_thread()

A per-thread CPU timer holds a reference to the PID of the thread it is attached to and, while it is armed, its node is queued in that thread's posix_cputimers. The task is looked up by that PID.

When a non-leader thread exec()s, de_thread() changes which task owns that PID. pid_task(timer->it.cpu.pid, PIDTYPE_PID) then returns NULL, but the node is still queued on tsk, which is alive. timer_lock_sighand() takes a failed lookup to mean that the node is already dequeued, so it has nothing to undo.

begin_new_exec() calls posix_cpu_timers_exit(me) right after exec_task_namespaces() and that removes the leftover node, so the state normally stays invisible. But bprm->point_of_no_return is set before de_thread(), so if unshare_files(), set_mm_exe_file(), exec_mmap() or exec_task_namespaces() fails, the task dies before it gets there. exit_itimers() then frees the k_itimer while its node is still queued, and reaping tsk later erases that freed node from the rbtree.

In short:

the non-leader thread B the parent

timer_create(CLOCK_THREAD_CPUTIME_ID) timer_settime() arm_timer() // the node is queued on B execve() de_thread(B) exchange_tids(B, leader) // B's PID now belongs to the leader release_task(leader) __exit_signal(leader) posix_cpu_timers_exit(leader) // cleans leader's queue, not B'…

GHSA-pr95-77xq-3v99

In the Linux kernel, the following vulnerability has been resolved:

exec: Cleanup POSIX timers right after de_thread()

A per-thread CPU timer holds a reference to the PID of the thread it is attached to and, while it is armed, its node is queued in that thread's posix_cputimers. The task is looked up by that PID.

In short:

the non-leader thread B the parent

msrc_CVE-2026-98260 — exec: Cleanup POSIX timers right after de_thread()

msrc_CVE-2026-98260

openSUSE-SU-2026:12131-1 — kernel-devel-7.2.10-1.1 on GA media

kernel-devel-7.2.10-1.1 on GA media

RHSA-2026:83707 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update

kernel: Bluetooth: hci_sync: fix stack buffer overflow in hci_le_big_create_sync kernel: Bluetooth: MGMT: validate LTK enc_size on load kernel: netfilter: nfnetlink_cthelper: fix OOB read in nfnl_cthelper_dump_table() kernel: scsi: target: configfs: Bound snprintf() return in tg_pt_gp_members_show() kernel: RDMA/vmw_pvrdma: Fix double free on pvrdma_alloc_ucontext() error path kernel: ipv6: validate extension header length before copying to cmsg kernel: ipv6: exthdrs: refresh nh after handling HAO option kernel: ipv6: exthdrs: refresh nh pointer after ipv6_hop_jumbo() kernel: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() kernel: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() kernel: ixgbevf: fix use-after-free in VEPA multicast source pruning kernel: ALSA: virtio: Validate control metadata from the device kernel: mm/khugepaged: write all dirty file folios when collapsing kernel: AMD-SN-7061: Safe RET Interrupt Vulnerability kernel: ipv6: fix use-after-free in ip6_finish_output2() kernel: exec: Cleanup POSIX timers right after de_thread()

UBUNTU-CVE-2026-98260

Affected: Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 194 more

In the Linux kernel, the following vulnerability has been resolved: exec: Cleanup POSIX timers right after de_thread() A per-thread CPU timer holds a reference to the PID of the thread it is attached to and, while it is armed, its node is queued in that thread's posix_cputimers. The task is looked up by that PID. When a non-leader thread exec()s, de_thread() changes which task owns that PID. pid_task(timer->it.cpu.pid, PIDTYPE_PID) then returns NULL, but the node is still queued on tsk, which is alive. timer_lock_sighand() takes a failed lookup to mean that the node is already dequeued, so it has nothing to undo. begin_new_exec() calls posix_cpu_timers_exit(me) right after exec_task_namespaces() and that removes the leftover node, so the state normally stays invisible. But bprm->point_of_no_return is set before de_thread(), so if unshare_files(), set_mm_exe_file(), exec_mmap() or exec_task_namespaces() fails, the task dies before it gets there. exit_itimers() then frees the k_itimer while its node is still queued, and reaping tsk later erases that freed node from the rbtree. In short: the non-leader thread B the parent timer_create(CLOCK_THREAD_CPUTIME_ID) timer_settime() arm_timer() // the node is queued on B execve() de_thread(B) exchange_tids(B, leader) // B's PID now belongs to the leader release_task(leader) __exit_signal(leader) posix_cpu_timers_exit(leader) // cleans leader's queue, not B's…