---
title: "CVE-2026-89922: CVE-2026-89922"
description: "In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Take srcu when importing watchpoint data __import_wp_info() backs up the original guest memory contents of a watchpoint with read_guest_abs(), which is kvm_read_guest() and therefore resolves the memslot via __kvm_memslots(). That requires kvm->srcu (or kvm->slots_lock) to be held, otherwise a concurrent memslot update can free the memslots array under us once its SRCU grace period has elapsed. As this is not fast path, following lock ordering (mutex first, then srcu) take the big hammer and hold the srcu for the full import."
url: https://panop.io/threat-heartbeat/CVE-2026-89922/
---

# CVE-2026-89922 CVE-2026-89922

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Take srcu when importing watchpoint data \_\_import\_wp\_info() backs up the original guest memory contents of a watchpoint with read\_guest\_abs(), which is kvm\_read\_guest() and therefore resolves the memslot via \_\_kvm\_memslots(). That requires kvm->srcu (or kvm->slots\_lock) to be held, otherwise a concurrent memslot update can free the memslots array under us once its SRCU grace period has elapsed. As this is not fast path, following lock ordering (mutex first, then srcu) take the big hammer and hold the srcu for the full import.

CVSS base score 7.8 /10

High

CISA KEV

Not listed

Public exploit

None known

EPSS

0.18% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-89922)

## Details

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Published

16 September 2026

Updated

15 October 2026

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-89922](https://nvd.nist.gov/vuln/detail/CVE-2026-89922)
- [https://git.kernel.org/stable/c/4c05bf21d1806853e662cc19e744736a3408f155](https://git.kernel.org/stable/c/4c05bf21d1806853e662cc19e744736a3408f155)
- [https://git.kernel.org/stable/c/6830fbc3724bf49c142aae69a4694f115fa9cedd](https://git.kernel.org/stable/c/6830fbc3724bf49c142aae69a4694f115fa9cedd)
- [https://git.kernel.org/stable/c/76f5b4ea9ed0aa5a34bda9d8a878f2c73026ec03](https://git.kernel.org/stable/c/76f5b4ea9ed0aa5a34bda9d8a878f2c73026ec03)
- [https://git.kernel.org/stable/c/a4e482def8533ebace517d9f67f1465841b1f982](https://git.kernel.org/stable/c/a4e482def8533ebace517d9f67f1465841b1f982)
- [https://git.kernel.org/stable/c/cc710ee45395efb4937e042960f791d33924e5f6](https://git.kernel.org/stable/c/cc710ee45395efb4937e042960f791d33924e5f6)
- [https://git.kernel.org/stable/c/f8e3a9997d5ecd56ebe4b262ff424516c068fecb](https://git.kernel.org/stable/c/f8e3a9997d5ecd56ebe4b262ff424516c068fecb)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)