{"vuln_id":"CVE-2026-64560","aliases":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nposix-cpu-timers: Prevent UAF caused by non-leader exec() race\n\nWongi and Jungwoo decoded and reported a non-leader exec() related race\nwhich can result in an UAF:\n\n sys_timer_delete()\t\t\texec()\n   posix_cpu_timer_del()\n   // Observes old leader\n   p = pid_task(pid, pid_type);\t\tde_thread()\n   \t\t\t\t\t  switch_leader();\n\t\t\t\t\t  release_task(old_leader)\n\t\t\t\t\t    __exit_signal(old_leader)\n\t\t\t\t\t      sighand = lock(old_leader, sighand);\n\t\t\t\t\t      posix_cpu_timers*_exit();\n   sighand = lock_task_sighand(p)\t      unhash_task(old_leader);\n     sh = lock(p, sighand)\t    \t      old_leader->sighand = NULL;\n\t\t\t\t\t      unlock(sighand);\n     (p->sighand == NULL)\n\tunlock(sh)\n\treturn NULL;\n\n   // Returns without action\n   if(!sighand)\n      return 0;\n   free_posix_timer();\n\nThis is \"harmless\" unless the deleted timer was armed and enqueued in\np->signal because on exec() a TGID targeted timer is inherited.\n\nAs sys_timer_delete() freed the underlying posix timer object\nrun_posix_cpu_timers() or any timerqueue related add/delete operations on\nother timers will access the freed object's timerqueue node, which results\nin an UAF.\n\nThere is a similar problem vs. posix_cpu_timer_set(). For regular posix\ntimers it just transiently returns -ESRCH to user space, but for the use\ncase in do_cpu_nanosleep() it's the same UAF just that the k_itimer is\nallocated on the stack.\n\nAlso posix_cpu_timer_rearm() fails to rearm the timer, which means it stops\nto expire.\n\nWhile debating solutions Frederic pointed out another problem:\n\n   posix_cpu_timer_del(tmr)\n\t\t\t\t\t__exit_signal(p)\n\t\t\t\t\t  posix_cpu_timers*_exit(p);\n\t\t\t\t\t  unhash_task(p);\n\t\t\t\t\t  p->sighand = NULL;\n     sh = lock_task_sighand(p)\n        sighand = p->sighand;\n\tif (!sighand)\n\t    return NULL;\n\tlock(sighand);\n\n     if (!sh)\n\tWARN_ON_ONCE(timer_queued(tmr));\n\nOn weakly ordered architectures it is not guaranteed that\nposix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit()\nwhen p->sighand is observed as NULL, which means the WARN() can be a false\npositive.\n\nSolve these issues by:\n\n  1) Changing the store in __exit_signal() to smp_store_release().\n\n  2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path\n     of lock_task_sighand().\n\n  3) Creating a helper function for looking up the task and locking sighand\n     which does not return when sighand == NULL. Instead it retries the\n     task lookup and only if that fails it gives up.\n\n  4) Using that helper in the three affected functions.\n\n#1/#2 ensures that the reader side which observes sighand == NULL also\nobserves all preceeding stores, i.e. the stores in posix_cpu_timers*_exit()\nand the ones in unhash_task().\n\n#3 ensures that the above described non-leader exec() situation is handled\ngracefully. When the task lookup returns the old leader, but sighand ==\nNULL then it retries. In the non-leader exec() case the subsequent task\nlookup will observe the new leader due to #1/#2. In normal exit() scenarios\nthe subsequent lookup fails.\n\nWhen the task lookup fails, the function also checks whether the timer is\nstill enqueued and issues a warning if that's the case. Unfortunately there\nis nothing which can be done about it, but as the task is already not\nlonger visible the timer should not be accessed anymore. This check also\nrequires memory ordering, which is not provided when the first lookup\nfails. To achieve that the check is preceeded by a smp_rmb() which pairs\nwith the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that\nthe stores in posix_cpu_timers*_exit() are visible.\n\nThe history of the non-leader exec() issue goes back to the early days of\nposix CPU timers, which stored a pointer to the group leader task in the\ntimer. That obviously fails when a non-leader exec() switches the leader.\ncommit e0a70217107e (\"posix-cpu-timers: workaround to suppress the problems\nwith mt exec\") added a temporary workaround for that in 2010 which surv\n---truncated---","published_at":"2026-07-29T17:16:53.637000Z","modified_at":"2026-11-13T18:20:08.020000Z","first_seen_at":"2026-11-22T13:39:59.999971Z","severity":"high","severity_source":"nvd","cvss_score":7.8,"cvss_vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","cwe":["CWE-416","CWE-362"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":0.0066,"epss_percentile":0.52476,"nvd_status":"Analyzed","enriched_at":"2026-11-22T16:00:35.794067Z","links":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64560"},"matched_alias":null,"items":[{"id":11961,"source":{"id":"grapheneos-releases","name":"GrapheneOS releases (grapheneos.org Atom)"},"title":"2026080500","summary":"Tags:\n\n2026080500 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold, Pixel 10a, emulator, generic, other targets)\n\nChanges since the 2026072900 release:\n\nfull 2026-08-05 Pixel security patch level\n\nupdate to August 2026 Pixel driver/firmware code\n\nkernel (Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL, Pixel 10 Pro Fold): apply fix for CVE-2026-0163\n\nContact Scopes: add a workaround for WhatsApp ACCOUNT_TYPE queries to resolve an incompatibility introduced with Android 17\n\nSandboxed Google Play compatibility layer: retain RPC provider connection for out-of-memory adjustment\n\nbackport Android 17 QPR1 fix for Bluetooth developer options confirmation\n\nkernel (6.1, 6.6, 6.12): backport patch for CVE-2026-64560\n\nkernel (6.1): update to latest GKI LTS branch revision\n\nkernel (6.6): update to latest GKI LTS branch revision\n\nkernel (6.12): update to latest GKI LTS branch revision\n\nVanadium: update to version 151.0.7922.71.0\n\nCamera: update to version 91\n\nCamera: update to version 92\n\nCamera: update to version 93\n\nPDF Viewer: update to version 33\n\nadevtool: add command for removing unused device images\n\nadevtool: improve the apply-bulletin-patches command\n\nAll of the Android 17 security patches from the current September 2026, October 2026, November 2026, December 2026 and January 2027 Android Security Bulletins are included in the 2026080501 security preview release. List of additional fixed CVEs:\n\nCritical: CVE-2026-28591, CVE-2026-28604, CVE-2026-28639, CVE-2026-28653, CVE-2026-28662, CVE-2026-28666, CVE-2026-45515, CVE-2026-45531, CVE-2026-49879, CVE-2026-49882, CVE-2026-49884, CVE-2026-49918, CVE-2026-49921, CVE-2026-49926, CVE-2026-49927, CVE-2026-49932, CVE-2026-49933, CVE-2026-55256, CVE-2026-55268, CVE-2026-55269, CVE-2026-55273, CVE-2026-55277, CVE-2026-55280, CVE-2026-58814, CVE-2026-58820, CVE-2026-58823, CVE-2026-58835, CVE-2026-58865, CVE-2026-58868, CVE-2026-58876, CVE-2026-58880, CVE-2026-58882\n\nHigh: CVE-2025-22442, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2026-0053, CVE-2026-28581, CVE-2026-28582, CVE-2026-28584, CVE-2026-28588, CVE-2026-28593, CVE-2026-28594, CVE-2026-28599, CVE-2026-28600, CVE-2026-28602, CVE-2026-28603, CVE-2026-28606, CVE-2026-28607, CVE-2026-28612, CVE-2026-28613, CVE-2026-28614, CVE-2026-28617, CVE-2026-28619, CVE-2026-28620, CVE-2026-28622, CVE-2026-28623, CVE-2026-28624, CVE-2026-28626, CVE-2026-28627, CVE-2026-28630, CVE-2026-28631, CVE-2026-28633, CVE-2026-28634, CVE-2026-28635, CVE-2026-28638, CVE-2026-28643, CVE-2026-28650, CVE-2026-28652, CVE-2026-28655, CVE-2026-28657, CVE-2026-28658, CVE-2026-28660, CVE-2026-28663, CVE-2026-28664, CVE-2026-28665, CVE-2026-28667, CVE-2026-28668, CVE-2026-28671, CVE-2026-45513, CVE-2026-45514, CVE-2026-45517, CVE-2026-45518, CVE-2026-45519, CVE-2026-45520, CVE-2026-45521, CVE-2026-45522, CVE-2026-45523, CVE-2026-45524, CVE-2026-45525, CVE-2026-45527, CVE-2026-45528, CVE-2026-45529, CVE-2026-49878, CVE-2026-49880, CVE-2026-49881, CVE-2026-49885, CVE-2026-49887, CVE-2026-49895, CVE-2026-49896, CVE-2026-49912, CVE-2026-49913, CVE-2026-49914, CVE-2026-49923, CVE-2026-49924, CVE-2026-49925, CVE-2026-49931, CVE-2026-49934, CVE-2026-49935, CVE-2026-49937, CVE-2026-55257, CVE-2026-55261, CVE-2026-55262, CVE-2026-55263, CVE-2026-55264, CVE-2026-55266, CVE-2026-55270, CVE-2026-55271, CVE-2026-55272, CVE-2026-55278, CVE-2026-55279, CVE-2026-55282, CVE-2026-55286, CVE-2026-55287, CVE-2026-55288, CVE-2026-55289, CVE-2026-55290, CVE-2026-55292, CVE-2026-55294, CVE-2026-58815, CVE-2026-58817, CVE-2026-58821, CVE-2026-58822, CVE-2026-58834, CVE-2026-58836, CVE-2026-58837, CVE-2026-58838, CVE-2026-58841, CVE-2026-58853, CVE-2026-58854, CVE-2026-58856, CVE-2026-58857, CVE-2026-58859, CVE-2026-58860, CVE-2026-58866, CVE-2026-58867, CVE-2026-58868, CVE-2026-58869, CVE-2026-58…","url":"https://grapheneos.org/releases","published_at":"2026-08-05T00:00:00Z","updated_at":"2026-08-05T00:00:00Z","fetched_at":"2026-11-22T13:39:59.936850Z","severity":"critical","cvss_score":9.8,"epss":0.07068,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":"CVE-2026-0163","vuln_ids":["CVE-2025-22442","CVE-2025-48564","CVE-2025-48565","CVE-2025-48566","CVE-2026-0053","CVE-2026-0163","CVE-2026-28581","CVE-2026-28582","CVE-2026-28584","CVE-2026-28588","CVE-2026-28591","CVE-2026-28593","CVE-2026-28594","CVE-2026-28599","CVE-2026-2860","CVE-2026-28600","CVE-2026-28602","CVE-2026-28603","CVE-2026-28604","CVE-2026-28606","CVE-2026-28607","CVE-2026-28612","CVE-2026-28613","CVE-2026-28614","CVE-2026-28617","CVE-2026-28619","CVE-2026-28620","CVE-2026-28622","CVE-2026-28623","CVE-2026-28624","CVE-2026-28626","CVE-2026-28627","CVE-2026-28630","CVE-2026-28631","CVE-2026-28633","CVE-2026-28634","CVE-2026-28635","CVE-2026-28638","CVE-2026-28639","CVE-2026-28643","CVE-2026-28650","CVE-2026-28652","CVE-2026-28653","CVE-2026-28655","CVE-2026-28657","CVE-2026-28658","CVE-2026-28660","CVE-2026-28662","CVE-2026-28663","CVE-2026-28664","CVE-2026-28665","CVE-2026-28666","CVE-2026-28667","CVE-2026-28668","CVE-2026-28671","CVE-2026-45513","CVE-2026-45514","CVE-2026-45515","CVE-2026-45517","CVE-2026-45518","CVE-2026-45519","CVE-2026-45520","CVE-2026-45521","CVE-2026-45522","CVE-2026-45523","CVE-2026-45524","CVE-2026-45525","CVE-2026-45527","CVE-2026-45528","CVE-2026-45529","CVE-2026-45531","CVE-2026-49878","CVE-2026-49879","CVE-2026-49880","CVE-2026-49881","CVE-2026-49882","CVE-2026-49884","CVE-2026-49885","CVE-2026-49887","CVE-2026-49895","CVE-2026-49896","CVE-2026-49912","CVE-2026-49913","CVE-2026-49914","CVE-2026-49918","CVE-2026-49921","CVE-2026-49923","CVE-2026-49924","CVE-2026-49925","CVE-2026-49926","CVE-2026-49927","CVE-2026-49931","CVE-2026-49932","CVE-2026-49933","CVE-2026-49934","CVE-2026-49935","CVE-2026-49937","CVE-2026-55256","CVE-2026-55257","CVE-2026-55261","CVE-2026-55262","CVE-2026-55263","CVE-2026-55264","CVE-2026-55266","CVE-2026-55268","CVE-2026-55269","CVE-2026-55270","CVE-2026-55271","CVE-2026-55272","CVE-2026-55273","CVE-2026-55277","CVE-2026-55278","CVE-2026-55279","CVE-2026-55280","CVE-2026-55282","CVE-2026-55286","CVE-2026-55287","CVE-2026-55288","CVE-2026-55289","CVE-2026-55290","CVE-2026-55292","CVE-2026-55294","CVE-2026-58814","CVE-2026-58815","CVE-2026-58817","CVE-2026-58820","CVE-2026-58821","CVE-2026-58822","CVE-2026-58823","CVE-2026-58834","CVE-2026-58835","CVE-2026-58836","CVE-2026-58837","CVE-2026-58838","CVE-2026-58841","CVE-2026-58853","CVE-2026-58854","CVE-2026-58856","CVE-2026-58857","CVE-2026-58859","CVE-2026-58860","CVE-2026-58865","CVE-2026-58866","CVE-2026-58867","CVE-2026-58868","CVE-2026-58869","CVE-2026-58876","CVE-2026-58880","CVE-2026-58882","CVE-2026-64560"],"tags":[],"cluster_id":11293,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/11961","html":"https://vulnwatch.ve1ve2.com/item/11961"}}]}