Skip to content
VulniPulse
High7.0Vendor: MediumRed Hat Linux

CVE-2026-98260: Red Hat Cleanup POSIX timers right after de_thread

This Red Hat advisory covers CVE-2026-98260 in Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions and Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions.

Open the Red Hat advisory

Key facts

Vendor rating
High, CVSS 7
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, .
CISA KEV
Not listed (catalogue checked )
Fixed in
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 and 15 more below
Source published
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Red Hat LinuxLinux Kernel

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.

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 remains referenced in an active queue.

A local user could exploit this vulnerability to trigger a use-after-free condition, leading to a system crash and Denial of Service (DoS) or potential privilege escalation. A lifecycle race in POSIX CPU timer handling can leave a timer node queued on a non-leader thread after de_thread changes ownership of its TID.

If exec later fails or is interrupted after the point of no return, exit_itimers can free the k_itimer while its node remains in the task timer tree.

Text from the source record.

How to fix CVE-2026-98260

Upgrade to a fixed release named by 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
  • kernel-rt-0:5.14.0-284.198.1.rt14.483.el9_2
  • kernel-0:5.14.0-427.156.1.el9_4
  • kernel-0:5.14.0-570.149.1.el9_6
  • RHSA-2026:85321
  • RHSA-2026:98608
  • RHSA-2026:83707
  • RHSA-2026:86033
  • RHSA-2026:97873
  • RHSA-2026:83738
  • RHSA-2026:83739
  • RHSA-2026:83797
  • RHSA-2026:83775

Vendor 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.

CVE-2026-98260 in other vendors' advisories

Compare every advisory for CVE-2026-98260

All Red Hat Linux advisories

Get an email when Red Hat Linux Kernel publishes the next one.

See Red Hat Linux Kernel'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.

Alert me about Red Hat Linux Kernel