PatchSiren cyber security CVE debrief
CVE-2026-89924 Linux CVE debrief
A memory leak vulnerability exists in the Linux kernel's KVM implementation for s390, specifically in the guest debug error path. The issue arises when the __import_wp_info() function allocates a per-watchpoint old_data buffer to back up the original guest memory contents, but fails to free these buffers in case of a later watchpoint import failure. This can lead to a memory leak of up to MAX_BP_COUNT - 1 buffers of up to MAX_WP_SIZE bytes per failed request. The vulnerability can be triggered by a repeated KVM_SET_GUEST_DEBUG request.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-16
- Original CVE updated
- 2026-10-19
- Advisory published
- 2026-09-16
- Advisory updated
- 2026-10-19
Who should care
Linux kernel developers and maintainers, KVM administrators and users, Linux distribution maintainers, security teams responsible for Linux systems, operators, and platform security teams responsible for vulnerability management and incident response planning.
Why it matters
The CVE-2026-89924 vulnerability is a memory leak issue in the Linux kernel's KVM implementation for s390. It affects Linux kernel developers, KVM administrators, and security teams responsible for Linux systems. The vulnerability can lead to increased memory usage and potential denial-of-service conditions. Fixing the vulnerability requires applying source code patches or updating the Linux kernel.
- Memory leak vulnerability can lead to increased memory usage and potential denial-of-service conditions
- Vulnerability can be triggered by a repeated KVM_SET_GUEST_DEBUG request
- Fixing the vulnerability requires applying source code patches or updating the Linux kernel
Technical summary
The vulnerability exists in the Linux kernel's KVM implementation for s390, specifically in the guest debug error path. The __import_wp_info() function allocates a per-watchpoint old_data buffer to back up the original guest memory contents. However, in case of a later watchpoint import failure, the function fails to free these buffers, leading to a memory leak. The vulnerability can be triggered by a repeated KVM_SET_GUEST_DEBUG request.
Defensive priority
Medium
Recommended defensive actions
- Review and apply the provided source code patches to fix the memory leak vulnerability
- Update Linux kernel to a version that includes the fix
- Monitor system memory usage to detect potential issues related to the vulnerability
- Perform a thorough review of the system configuration to ensure that it is secure
- Implement additional monitoring and logging to detect potential security incidents
- Conduct a risk assessment to determine the potential impact of the vulnerability on the system
- Review and update the incident response plan to ensure that it is effective in responding to potential security incidents
Evidence notes
The CVE record and source item provide details about the vulnerability, including its description, affected versions, and references to source code changes. However, the corpus does not provide information on exploitation or specific attack vectors.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-89924 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-89924
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-89924 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89924
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
KVM: s390: Fix old_data leak in guest debug error path
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/89xxx/CVE-2026-89924.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/124c81ee610e1fbdd93d4399f88d9e28ba97a941
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/e5ae7816e5ad145618f7fd568a0e8a94dd9f81f4
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/c85d402553987777cc4742751437ea5dcbf98a7b
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/5fbf319137735252eefa507193c9a619af5b7457
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/4048d0a252163084794be3e37995b872c5178913
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/f55e4d415d95342d5753e528e05a1e8623992c3f
Supplemental source
-
Source reference
Unverified legacy reference
URL: https://git.kernel.org/stable/c/46cb8a273e2f853f89a78b59dbdff8787b6e1c86
Supplemental source
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.