Dismissed
(max. allowed matches exceeded)
Permalink
CVE-2026-89922
7.8 HIGH
- CVSS version (CVSS): 3.1
- Attack Vector (AV): Local (L)
- Attack Complexity (AC): Low (L)
- Privileges Required (PR): Low (L)
- User Interaction (UI): None (N)
- Scope (S): Unchanged (U)
- Confidentiality (C): High (H)
- Integrity (I): High (H)
- Availability (A): High (H)
- Modified Attack Vector (MAV): Local (L)
- Modified Attack Complexity (MAC): Low (L)
- Modified Privileges Required (MPR): Low (L)
- Modified User Interaction (MUI): None (N)
- Modified Confidentiality (MC): High (H)
- Modified Scope (MS): Unchanged (U)
- Modified Integrity (MI): High (H)
- Modified Availability (MA): High (H)
Activity log
- Created & dismissed (max. allowed matches exceeded) suggestion
KVM: s390: Take srcu when importing watchpoint data
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.
References
Affected products
Linux
- =<7.2.*
- <4c05bf21d1806853e662cc19e744736a3408f155
- =<6.1.*
- <76f5b4ea9ed0aa5a34bda9d8a878f2c73026ec03
- =<6.12.*
- <6830fbc3724bf49c142aae69a4694f115fa9cedd
- =<6.18.*
- =<*
- <3.16
- ==3.16
- <cc710ee45395efb4937e042960f791d33924e5f6
- =<6.6.*
- <f8e3a9997d5ecd56ebe4b262ff424516c068fecb
- <a4e482def8533ebace517d9f67f1465841b1f982