{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64560 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64560 is a high-severity use after free vulnerability in Linux, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64560 and fix it if it is affected.\n\nWhat it is: CVE-2026-64560 is a high-severity use after free vulnerability in Linux, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-64560 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-64560/ (Markdown: https://insights.sbomify.com/CVE-2026-64560/index.md)","id":"CVE-2026-64560","markdown":"https://insights.sbomify.com/CVE-2026-64560/index.md","name":"CVE-2026-64560","record":{"aliases":["AZL-94148","BELL-CVE-2026-64560","DEBIAN-CVE-2026-64560","GHSA-78ph-mc3q-52vv","ROOT-OS-DEBIAN-12-CVE-2026-64560","UBUNTU-CVE-2026-64560"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in Linux kernel posix-cpu-timers allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"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-\u003esighand = NULL;\n\t\t\t\t\t      unlock(sighand);\n     (p-\u003esighand == 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-\u003esignal 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-\u003esighand = NULL;\n     sh = lock_task_sighand(p)\n        sighand = p-\u003esighand;\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-\u003esighand 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---","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-07-23","github_poc":20,"max_poc_stars":80,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-03T12:36:27Z","kind":"github_poc","ref":"https://github.com/villager1314/CVE-2026-64560-Analysis","stars":80,"title":null},{"date":"2026-10-15T14:19:23Z","kind":"github_poc","ref":"https://github.com/feiguang-ai/plz110-6.12.69-cve-2026-64560-ksu","stars":31,"title":"一加 15T（PLZ110）临时 root + KernelSU per-boot 接管：CVE-2026-64560 移植，不写分区、重启即失效。内核 6.12.69-android16-6-g242e1a07f878。"},{"date":"2026-10-19T05:30:01Z","kind":"github_poc","ref":"https://github.com/Feng1586/CVE-2026-64560-public","stars":23,"title":"CVE-2026-64560 staged security research package"},{"date":"2026-09-05T11:06:27Z","kind":"github_poc","ref":"https://github.com/quyicheng03-boop/xiaomi15-dada-cve-2026-64560","stars":21,"title":"Device-bound CVE-2026-64560 adaptation for Xiaomi 15 dada OS4.0.0.8"},{"date":"2026-09-24T17:36:00Z","kind":"github_poc","ref":"https://github.com/a23bc/op13-cve-2026-64560","stars":15,"title":null},{"date":"2026-10-20T09:43:06Z","kind":"github_poc","ref":"https://github.com/Yunnijian/OnePlus16-Jailbreak","stars":12,"title":"OnePlus 16 (PYB110) jailbreak: CVE-2026-64560 + CVE-2026-98260 + KernelSU / KernelSU Next / BakaSU / SukiSU Ultra LKM"},{"date":"2026-09-26T12:31:39Z","kind":"github_poc","ref":"https://github.com/qingle009/opace6-cve-2026-64560","stars":10,"title":"OnePlus Ace 6 temporary root tool (CVE-2026-64560) - device-verified port with corrected bootidParent address"},{"date":"2026-09-25T13:42:42Z","kind":"github_poc","ref":"https://github.com/Wangs-official/opace6-cve-2026-64560","stars":7,"title":"针对 OnePlus Ace6 设备的 cve-2026-64560 复现"}],"tier":"poc_unverified"},"has_fix":true,"headline":"posix-cpu-timers: Prevent UAF caused by non-leader exec() race","id":"CVE-2026-64560","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"KVM: x86: Check for invalid/obsolete root *after* making MMU pages available","id":"CVE-2026-64561"},"packages":[],"prev":{"headline":"s390/pkey: Check length in PKEY_VERIFYPROTK ioctl","id":"CVE-2026-64559"},"products":["Linux"],"published":"2026-07-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A race condition in Linux kernel posix-cpu-timers allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-64560/"}