nday
CVE-2026-98260

exec: Cleanup POSIX timers right after de_thread()

Linux / Linux

A public PoC appeared 42 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. Listed by 1 of 4 PoC sources: github. Not in CISA KEV.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
POC
disclosed
disclosure → PoC
T+42d POC is date-only
cvss
7.8 HIGH v3.1

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
10-06T08:45Z
PATpatch
no record yet
ANAanalysis
10-16T16:00Z
POCPoC
11-17, date only
ITWexploited
no record yet
KEVKEV
no record yet

Summary

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() ]

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

Event log

+DISdisclosed

CVE record published by Linux. CVSS 7.8, high.

src cvelist · nday , bulk import · raw
{
  "id": 457556,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-98260",
  "occurred_at": "2026-10-06T08:45:24.711Z",
  "observed_at": "2026-11-13T05:40:20.493151Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 7.8,
      "base_severity": "HIGH"
    },
    "state": "PUBLISHED",
    "date_published": "2026-10-06T08:45:24.711Z",
    "assigner_short_name": "Linux"
  }
}
+ANAtechnical analysis

Posted to the oss-security mailing list: “Infinity Core: Linux Kernel Core LPEs”.

src osssec 2026/q4/211 · nday , observed live · raw
{
  "id": 495524,
  "type": "analysis_published",
  "source": "osssec",
  "url": "https://seclists.org/oss-sec/2026/q4/211",
  "occurred_at": "2026-10-16T16:00:19Z",
  "observed_at": "2026-11-20T08:13:28.642196Z",
  "is_backfill": false,
  "dedupe_key": "2026/q4/211",
  "detail": {
    "list": "oss-security",
    "author": "Hyunwoo Kim",
    "subject": "Infinity Core: Linux Kernel Core LPEs",
    "is_reply": false
  }
}
2026-11-17date only, from source
+POCpublic PoC

PoC repository on GitHub: yxc0915/cve-2026-98260-ppg-an00. The date is the repository's creation day.

src github 1461985364 · nday , observed live · raw
{
  "id": 497961,
  "type": "poc_published",
  "source": "github",
  "url": "https://github.com/yxc0915/cve-2026-98260-ppg-an00",
  "occurred_at": "2026-11-17T21:21:32Z",
  "observed_at": "2026-11-20T00:00:00Z",
  "is_backfill": false,
  "dedupe_key": "1461985364",
  "detail": {
    "url": "https://github.com/yxc0915/cve-2026-98260-ppg-an00",
    "title": "yxc0915/cve-2026-98260-ppg-an00",
    "precision": "day"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.