powerpc/xive: propagate IPI init errors to prevent use-after-free
CVE-2026-93260 · published 24 Sept 2026
How serious is it
- Severity: high, CVSS score 7.4 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-93260?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 243e25112d06b348f087a6f7aba4bbc288285bdd to < e36b1c2eafcaaddefa70d55e6fda74cf6cda38af, 243e25112d06b348f087a6f7aba4bbc288285bdd to < 2ea6238343691309e68308131c7e80c3ae05afea, 243e25112d06b348f087a6f7aba4bbc288285bdd to < 5c9ab0c9cede9f149733d330e2d7d45341b71359, 243e25112d06b348f087a6f7aba4bbc288285bdd to < c554a8d376d5aea1b237ed6bef6f9fbfc550e67f
- Linux Linux: 4.12
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
powerpc/xive: propagate IPI init errors to prevent use-after-free
When xive_init_ipis() fails (e.g. irq_domain_alloc_irqs() fails),
the error path frees the global xive_ipis array. However,
xive_smp_probe() previously ignored this failure and proceeded to
call xive_setup_cpu_ipi(), which dereferences the already-freed
xive_ipis pointer -- a use-after-free.
Now that xive_smp_probe() returns int (previous patch), propagate
the error from xive_init_ipis() and xive_setup_cpu_ipi() through
xive_smp_probe(). Check the return value in both pnv_smp_probe()
and pSeries_smp_probe() so that IPI setup is aborted cleanly on
failure, avoiding the use-after-free.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/e36b1c2eafcaaddefa70d55e6fda74cf6cda38af
- git.kernel.org/stable/c/2ea6238343691309e68308131c7e80c3ae05afea
- git.kernel.org/stable/c/5c9ab0c9cede9f149733d330e2d7d45341b71359
- git.kernel.org/stable/c/c554a8d376d5aea1b237ed6bef6f9fbfc550e67f
- git.kernel.org/stable/c/411a3c016e7a95f5fa105a0587e07d0647a77727
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON