KernelScan.io

HIGH Public PoC Introduced in 5.7

exec CpuTimer UAF

CVE-2026-98260

CVSS 7.8 / 10.0 NVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

KernelScan AI7.4HIGH

01

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 __unhash_process(leader) // that PID has no task anymore exec_mmap() mmap_read_lock_killable(old_mm) kill(B, SIGKILL) // -EINTR get_signal() do_exit() exit_itimers() posix_timer_delete() posix_cpu_timer_del() posix_timer_unhash_and_free() // freed while still queued wait4() release_task(B) posix_cpu_timers_exit(B) cleanup_timerqueue() timerqueue_del() // use-after-free Move the POSIX timer cleanup right after de_thread() before any of the later failure conditions brings the task into do_exit(). [ tglx: Move the cleanup right after de_thread() ]

02

Engine v0.7.0

Risk summary

A local unprivileged user can trigger a use-after-free in the kernel's POSIX CPU timer handling during execve, potentially leading to privilege escalation or kernel code execution. The exploit requires winning a narrow race window but needs no special capabilities or hardware. Systems allowing untrusted local code—including containers and multi-tenant hosts—are most at risk.

Affectedfs/exec.c (exec / POSIX CPU timers)

Vulnerability analysis

When a non-leader thread that has an armed per-thread CPU timer calls execve, the exec path swaps thread IDs so that the timer's PID lookup no longer finds the original task. The timer node remains queued on the living task, but the cleanup that would remove it runs only later in the exec sequence. If a subsequent step fails or the thread is killed at the right moment, the thread exits before that cleanup happens, and the timer object is freed while its node is still in the task's timer queue. Reaping the task later tries to delete the freed node, causing a use-after-free. The fix moves the POSIX timer cleanup to immediately after the thread ID swap, so no later failure can leave the queued node behind. Any local unprivileged user can trigger this by creating a per-thread CPU timer, arming it, calling execve from a non-leader thread, and racing a SIGKILL delivery; no special privileges or hardware are required.

Exploit availability

KernelScan found public exploit code for this CVE. Open it in the CVE browser to see what we found, where, and how strong the evidence is — that needs a free account with a confirmed email address.

03

BranchIntroducedFixed inPatch commit
6.15.76.1.191f6c93e8ecaaf
6.125.76.12.112d9ae467e617c
6.185.76.18.5475aa08b93c65
6.65.76.6.1586f1977cea3e8
7.25.77.2.8d602877baf36
mainline5.77.3acb03d388181
cip/6.125.76.12.112-cip33d9ae467e617c

04

State of the newest release of each Civil Infrastructure Platform SLTS tree, from CIP's own fix records.

CIP treeState
cip/6.12Fixed in 6.12.112-cip33
cip/6.1Affected — no CIP fix yet (latest 6.1.190-cip62)
cip/6.1-rtAffected — no CIP fix yet (latest 6.1.189-cip61-rt32)
cip/5.10Affected — no CIP fix yet (latest 5.10.272-cip79)
cip/5.10-rtAffected — no CIP fix yet (latest 5.10.272-cip79-rt35)