PoC Monitor
← All CVEs
CVE-2026-98258published 6 Oct 2026 08:45 UTCData: JSON · API

Linux

posix-cpu-timers: Prevent freeing a timer which is queued on the expiry list

In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent freeing a timer which is queued on the expiry list Kijo analyzed another race in the POSIX CPU timer code: Commit bf635681c906 converted cpu_timer::firing from a tristate value to a boolean. This lost the distinction between "not owned by the firing list" and "still owned, but delivery was canceled". The resulting race is: expiry handler timer_settime() timer_delete() -------------- --------------- -------------- collect timer onto private firing list firing = true observes firing = true firing = false return TIMER_RETRY wait for handler observes firing = false finish deletion unhash and free timer resume list traversal read freed elist.next -> UAF The firing bit is clearly the wrong indicator since that commit. Check whether the timer is queued on the expiry list or not instead. If it is queued clear the firing bit to prevent signal delivery as before and return TIMER_RETRY so the caller unlocks the timer which allows the expiry code to make progress and remove it from the list.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= bf635681c906ad056d1fda325de8d1c12c9f8201, < 9971dac1a77845ff467146915fcbb9170f6a8209
  • >= bf635681c906ad056d1fda325de8d1c12c9f8201, < 4336e3f47d9d516441066e9a65eaf076790d8d45
  • >= bf635681c906ad056d1fda325de8d1c12c9f8201, < c21eaa72f02fc6e85621cbe09d303d8fb8bd39cd

Fixed in 9971dac1a77845ff467146915fcbb9170f6a8209, 4336e3f47d9d516441066e9a65eaf076790d8d45, c21eaa72f02fc6e85621cbe09d303d8fb8bd39cd

Linux Linux
  • 6.13

Fixed in 0, 6.18.54, 7.2.8, 7.3

Mitigation

Upgrade Linux to 9971dac1a77845ff467146915fcbb9170f6a8209 or 4336e3f47d9d516441066e9a65eaf076790d8d45 or c21eaa72f02fc6e85621cbe09d303d8fb8bd39cd or later.

Upgrade Linux to 0 or 6.18.54 or 7.2.8 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published6 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

2 pending

Pending 2
RepositoryCreatedFound by usStarsAssessment
imkidz0/Trilemma 1 Nov 2026 +26 d 14 Nov 2026 0 Pending · repository exceeds size limit
Flags · score 15
  • owner account created less than 30 days before the repo

Below the suspicion threshold (50); does not change the assessment.

imkidz0/poc-CVE-2026-98258 1 Nov 2026 +26 d 14 Nov 2026 0 Pending · repository exceeds size limit via PoC Index
Flags · score 15
  • owner account created less than 30 days before the repo

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.