CVE-2026-98260: exec: Cleanup POSIX timers right after de_thread()
CVE-2026-98260 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- High
- CVSS base score
- 7 (NetApp), 7 (Red Hat)
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H· base score 7.8, scored by LinuxAttack vector: local. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: high.- EPSS
- 0.22% chance of exploitation in the next 30 days (12th percentile). FIRST EPSS, .
- Fixed releases
- Red Hat: kernel-0:6.12.0-211.67.1.el10_2, kernel-0:6.12.0-264.14.1.el10_3, kernel-0:6.12.0-55.111.1.el10_0, kernel-0:5.14.0-687.59.1.el9_8, kernel-0:5.14.0-741.20.1.el9_9, kernel-0:5.14.0-284.198.1.el9_2 and 12 more in the advisory
- Assigned by
- Linux (CNA)
- CVE record published
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-98260; each belongs to its advisory, not to every product listed. How records are collected and checked.
Description
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() ]
Text from the CVE.org record (Linux).
How do I fix CVE-2026-98260?
Upgrade to a fixed release named by the vendor:
- Red Hat: kernel-0:6.12.0-211.67.1.el10_2, kernel-0:6.12.0-264.14.1.el10_3, kernel-0:6.12.0-55.111.1.el10_0, kernel-0:5.14.0-687.59.1.el9_8, kernel-0:5.14.0-741.20.1.el9_9, kernel-0:5.14.0-284.198.1.el9_2
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. (Red Hat)
Vendor advisories for CVE-2026-98260
NetApp
1 advisory- Advisory severityHigh7.0
High [CVE-2026-98260] Linux Kernel Vulnerability in NetApp Products
NTAP-20261113-0011Source published Source updated
Linux kernel versions 5.7-rc1 through 6.6.157, 6.7-rc1 through 6.12.111, 6.13-rc1 through 6.18.53, 6.19-rc1 through 7.2.7 and 7.3-rc1 through 7.3-rc3 are susceptible to a vulnerability which when successfully exploited could allow a local attacker to cause a system crash and Denial of Service (DoS) or escalate privileges. Successful exploitation of this vulnerability could lead to disclosure of sensitive information, addition or modification of data or Denial of Service (DoS). NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. NetApp states there is no workaround available at this time.
- Affected products in this advisory
- No product details extracted. Check the source bulletin.
- Source-reported affected versions
- 6.6.157
- 6.12.111
- 6.13
- 6.18.53
2 more entries in the full advisory.
- Source-reported fixed versions
- No fixed-version detail extracted. This does not mean no fix exists.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
Red Hat
1 advisory- Advisory severityHigh7.0
High [CVE-2026-98260] Cleanup POSIX timers right after de_thread
CVE-2026-98260Source published Source updated
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. 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. When a multi-threaded program sets up a per-thread timer and executes a new program that subsequently fails during startup, the kernel can free timer memory while it…
- Affected products in this advisory
- Red Hat Enterprise Linux 10.0 Extended Update Support
- Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions
- Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions
- Red Hat Enterprise Linux 9.6 Extended Update Support
2 more entries in the full advisory.
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- kernel-0:6.12.0-211.67.1.el10_2
- kernel-0:6.12.0-264.14.1.el10_3
- kernel-0:6.12.0-55.111.1.el10_0
- kernel-0:5.14.0-687.59.1.el9_8
14 more entries in the full advisory.
- Mitigation guidance
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
References
- CVE-2026-98260 recordCVE.org
- CVE-2026-98260 detailNVD
- git.kernel.org/stable/c/f6c93e8ecaaf12959b7ef6eb611351001db2ff5d
- git.kernel.org/stable/c/6f1977cea3e85cd8ab55fb337d3e1725fe61d1ce
- git.kernel.org/stable/c/d9ae467e617ca29b825493a362bf0d75ad5f4ac3
- git.kernel.org/stable/c/75aa08b93c65766040f9ca99f41ac85ad22596b6
- git.kernel.org/stable/c/d602877baf36c43c788a5f472c977e0be414029f
- git.kernel.org/stable/c/acb03d3881818581052924a9bbbe92b8741ed448
Timeline
- CVE record published
- First vendor advisory listed by VulniPulse
- CVE record last updated
More NetApp advisories
CVE-2026-121810Nov 18, 2026NGINX Vulnerability in NetApp ProductsCVE-2026-113425Nov 18, 2026NGINX Vulnerability in NetApp ProductsCVE-2026-114946Nov 18, 2026Java SE Vulnerability in NetApp ProductsCVE-2026-114945Nov 18, 2026Java SE Vulnerability in NetApp ProductsCVE-2026-123634Nov 18, 2026NGINX Vulnerability in NetApp ProductsCVE-2026-114943Nov 18, 2026Java SE Vulnerability in NetApp Products
Get an email when NetApp publishes the next one.
See NetApp's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.