PoC Monitor
← All CVEs
CVE-2026-64560published 29 Jul 2026 16:47 UTCData: JSON · API

Linux

posix-cpu-timers: Prevent UAF caused by non-leader exec() race

In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader->sighand = NULL; unlock(sighand); (p->sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p->signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p->sighand = NULL; sh = lock_task_sighand(p) sighand = p->sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p->sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated---

First public PoC 6.3 days beforebefore publication · 23 Jul 2026
Public PoCs1515 on GitHub · +1 suspicious, not counted
CVSS7.8high · scored by CNA · CWE-362
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59, < 67aa823e3e8c229c6d374df79c804f6721cb83b6
  • >= 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59, < d8bcb28abad857f1415da7656f19b2ada90af04f
  • >= 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59, < cc35ddbc497311e0b6b9a6a6a4f4d1217d6ab1aa
  • >= 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59, < 12a891c773aeb5823d63dbd0cb2ab931d6c21c9b
  • >= 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59, < e74443f5db0037c556ef436fa64b88bf4ea08f83
  • >= 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59, < 6a7ecc25abe6f0fecc6e62a05096987200edbd02
  • >= 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59, < ad1cafa1bdaa71da85d71cac053838bbe97852b6
  • >= 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59, < 920f893f735e92ba3a1cd9256899a186b161928d

Fixed in 67aa823e3e8c229c6d374df79c804f6721cb83b6, d8bcb28abad857f1415da7656f19b2ada90af04f, cc35ddbc497311e0b6b9a6a6a4f4d1217d6ab1aa, 12a891c773aeb5823d63dbd0cb2ab931d6c21c9b, e74443f5db0037c556ef436fa64b88bf4ea08f83, 6a7ecc25abe6f0fecc6e62a05096987200edbd02, ad1cafa1bdaa71da85d71cac053838bbe97852b6, 920f893f735e92ba3a1cd9256899a186b161928d

Linux Linux
  • 5.7

Fixed in 0, 5.10.262, 5.15.213, 6.1.180, 6.6.147, 6.12.100, 6.18.41, 7.1.5, 7.2

Mitigation

Upgrade Linux to 67aa823e3e8c229c6d374df79c804f6721cb83b6 or d8bcb28abad857f1415da7656f19b2ada90af04f or cc35ddbc497311e0b6b9a6a6a4f4d1217d6ab1aa or 12a891c773aeb5823d63dbd0cb2ab931d6c21c9b or e74443f5db0037c556ef436fa64b88bf4ea08f83 or 6a7ecc25abe6f0fecc6e62a05096987200edbd02 or ad1cafa1bdaa71da85d71cac053838bbe97852b6 or 920f893f735e92ba3a1cd9256899a186b161928d or later.

Upgrade Linux to 0 or 5.10.262 or 5.15.213 or 6.1.180 or 6.6.147 or 6.12.100 or 6.18.41 or 7.1.5 or 7.2 or later.

Timeline

Days relative to CVE publication
-8-6-4-2t=0+2+4+6+8First public PoC23 Jul 2026 · t−6.3dCVE published29 Jul 2026 · t = 0

First public PoC 6.3 days before publication; not in CISA KEV. First PoC: imkidz0/CVE-2026-64560-exploit (created 23 Jul 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

15 PoCs · 3 pending · 3 informational · 9 suspicious or fake

PoCs 15
RepositoryCreatedFound by usStarsAssessment
imkidz0/CVE-2026-64560-exploit 23 Jul 2026 −6.3 d backfilled 2 PoC
imkidz0/exploit-CVE-2026-64560 23 Jul 2026 −6.3 d backfilled 2 PoC
itsmichiya/exploit-CVE-2026-64560 23 Jul 2026 −6.3 d backfilled 2 PoC
villager1314/CVE-2026-64560-Analysis 3 Aug 2026 +4.8 d backfilled 82 PoC
Flags · score 15
  • no network code found (normal for a local exploit)

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

quyicheng03-boop/xiaomi15-dada-cve-2026-64560 5 Sep 2026 +38 d backfilled 23 PoC
RMDycz/K80Pro-miro-CVE-2026-64560 18 Sep 2026 +51 d backfilled 0 PoC
a23bc/op13-cve-2026-64560 24 Sep 2026 +57 d backfilled 15 PoC
Become-ILLUSORY/cve-2026-64560-a16 25 Sep 2026 +58 d backfilled 6 PoC
Flags · score 40
  • contains executables (bin/cve-2026-64560-fanout, bin/cve-2026-64560-fanout-op13, bin/cve-2026-64560-fanout-rmx5010-a16)

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

Wangs-official/opace6-cve-2026-64560 25 Sep 2026 +58 d backfilled 7 PoC
qingle009/opace6-cve-2026-64560 26 Sep 2026 +59 d backfilled 12 PoC
Meniben/redmi14c-pond-cve-2026-64560 2 Oct 2026 +65 d backfilled 0 PoC
feiguang-ai/plz110-6.12.69-cve-2026-64560-ksu 15 Oct 2026 +78 d 14 Nov 2026 34 PoC
maosasagawa/pmx110-cve-2026-64560 17 Oct 2026 +80 d 14 Nov 2026 1 PoC
Flags · score 25
  • contains archives (installerx-default/dhizuku-api.aar, installerx-default/installerx-default.apk)

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

ChaYeWuu/prague-CVE-2026-64560-OS4.0 17 Oct 2026 +80 d 14 Nov 2026 6 PoC
exumeOAO/plr110-6.12.38-cve-2026-64560-ksu 31 Oct 2026 +94 d 14 Nov 2026 0 PoC
Pending 3
RepositoryCreatedFound by usStarsAssessment
Sulisong/OnePlus16-Jailbreak 20 Oct 2026 +83 d 14 Nov 2026 0 Pending · repository exceeds size limit
TKgbUssr/KozRoot-PMX110-6.18.21 3 Nov 2026 +97 d 14 Nov 2026 7 Pending · repository exceeds size limit via PoC Index
Yunnijian/OnePlus16-Jailbreak unknown backfilled 0 Pending · repository unavailable (HTTP 404) via PoC Index · not checked yet
Informational 3
RepositoryCreatedFound by usStarsAssessment
249707737/Android-16-SM7550-Kernel-5.15.178-Exploit-Research 19 Aug 2026 +21 d backfilled 1 Informational · write-up
sangsheng2026/honor-90gt-mag-an00-root-research 9 Oct 2026 +72 d backfilled 3 Informational · list
Flags · score 15
  • owner account created less than 30 days before the repo

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

aucai/Redmi-K90-CVE-2026-64560 30 Oct 2026 +93 d 14 Nov 2026 0 Informational · write-up
Suspicious or fake 9
RepositoryCreatedFound by usStarsAssessment
d1667018881/myroot 30 Jul 2026 +9 h backfilled 11 Fake
000999888111/op13-cve-2026-64560 4 Oct 2026 +67 d backfilled 0 Fake
totsiaw/cve-2026-64560-rmx6699 17 Oct 2026 +80 d 14 Nov 2026 2 Fake
Feng1586/CVE-2026-64560-public 19 Oct 2026 +82 d 14 Nov 2026 28 Fake
Feng1586/CVE-2026-64560-sources 19 Oct 2026 +82 d 14 Nov 2026 1 Suspicious · score 100
Why suspicious
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/guide/how-to-build.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/guide/how-to-integrate-for-non-gki.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/id_ID/guide/how-to-build.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/id_ID/guide/how-to-integrate-for-non-gki.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/ja_JP/guide/how-to-build.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/ja_JP/guide/how-to-integrate-for-non-gki.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/pt_BR/guide/how-to-build.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/pt_BR/guide/how-to-integrate-for-non-gki.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/ru_RU/guide/how-to-build.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/ru_RU/guide/how-to-integrate-for-non-gki.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/vi_VN/guide/how-to-build.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/vi_VN/guide/how-to-integrate-for-non-gki.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/zh_CN/guide/how-to-build.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/zh_CN/guide/how-to-integrate-for-non-gki.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/zh_TW/guide/how-to-build.md
  • pipes a download into a shell / encoded PowerShell in vendor/KernelSU/website/docs/zh_TW/guide/how-to-integrate-for-non-gki.md
  • contains executables (vendor/KernelSU-Next/userspace/ksud/bin/aarch64/bootctl, vendor/KernelSU-Next/userspace/ksud/bin/aarch64/waitsys, vendor/KernelSU-Next/userspace/ksud/bin/riscv64/waitsys)
  • large base64 blob in code in vendor/KernelSU-Next/manager/app/src/main/assets/eruda.min.js
TKgbUssr/PMX110-6.18.21-exploit 22 Oct 2026 +85 d 14 Nov 2026 10 Fake
No-World/rootkit 24 Oct 2026 +87 d 14 Nov 2026 9 Fake
wanwuzhishi/ksu-root 25 Oct 2026 +88 d 14 Nov 2026 5 Fake
youssefnoser/opd2415-6.6.118-cve-2026-64560-ksu 27 Oct 2026 +90 d 14 Nov 2026 1 Fake

Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. "Backfilled" means we found the repository more than 30 days after it was created. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.