GHSA-HQR4-MV6V-VC35
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: Fix IRQ injection with SIGP Stop and Store Status
When __inject_sigp_stop() is called for a Stop and Store Status operation, if the vCPU is running, the interrupt is marked as pending and the status is stored by the thread performing the KVM_RUN IOCTL.
If the vCPU is already stopped, the status is stored immediately.
Storing the status means writing into userspace, which might fault, and __inject_sigp_stop() is called from do_inject_vcpu() which in turn is always called holding a spinlock, which is obviously an issue.
Fix this by returning -EWOULDBLOCK from __inject_sigp_stop(), and adding a bool flag to indicate whether a store status is needed. The callers of do_inject_vcpu() are modified to pass the pointer to the bool flag; whenever a Store Status operation is needed, the callers can now perform it outside the spinlock.
Opportunistically refactor kvm_s390_set_irq_state() to use scoped_guard() and __free().
[ Added Fixes tag while picking -- Claudio ]
{
"affected": [],
"aliases": [
"CVE-2026-98930"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:13Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: Fix IRQ injection with SIGP Stop and Store Status\n\nWhen __inject_sigp_stop() is called for a Stop and Store Status\noperation, if the vCPU is running, the interrupt is marked as pending\nand the status is stored by the thread performing the KVM_RUN IOCTL.\n\nIf the vCPU is already stopped, the status is stored immediately.\n\nStoring the status means writing into userspace, which might fault, and\n__inject_sigp_stop() is called from do_inject_vcpu() which in turn is\nalways called holding a spinlock, which is obviously an issue.\n\nFix this by returning -EWOULDBLOCK from __inject_sigp_stop(), and\nadding a bool flag to indicate whether a store status is needed. The\ncallers of do_inject_vcpu() are modified to pass the pointer to the\nbool flag; whenever a Store Status operation is needed, the callers can\nnow perform it outside the spinlock.\n\nOpportunistically refactor kvm_s390_set_irq_state() to use\nscoped_guard() and __free().\n\n[ Added Fixes tag while picking -- Claudio ]",
"id": "GHSA-hqr4-mv6v-vc35",
"modified": "2026-10-23T15:31:31Z",
"published": "2026-10-23T15:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98930"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3bd77c59576b1d447fd56cc689ae9523a334b924"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a379ac504fcb8c6fc2aa36203f5489b9581eb2e0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d0e3bf633f0585a0c2c2105ea7723777d764fae5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d343407b728a80b74be3c24b59f15e60289ea527"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.