Skip to content
Heist/ feed
Back to feed
UnratedFix available

KVM: s390: Fix IRQ injection with SIGP Stop and Store Status

Type: advisorySources: OSV

In 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 ]

Products
Kernel
Affected versions
Not specified
Fixed versions
6.12.112, 6.18.55, 7.2.9
CVEs
CVE-2026-98930
Confirmed fixed CVEs
Not specified
Updated in this feed
8 Nov 2026, 02:39 UTC · Revision 1

Source evidence

KVM: s390: Fix IRQ injection with SIGP Stop and Store Status

core-osv · Original source

Published 23 Oct 2026, 12:08 UTC

In 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 ]

osv:CVE-2026-98930

Kernel

Fixed versions: 6.12.112, 6.18.55, 7.2.9

Complete source record
{
  "id": "60c0392a6079e41c423759e53223f448dce715a65c8ba00543e1e5cb72591f0e",
  "url": "https://osv.dev/vulnerability/CVE-2026-98930",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "KVM: s390: Fix IRQ injection with SIGP Stop and Store Status",
    "summary": "In 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 ]",
    "evidence": "osv:CVE-2026-98930",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.12.112",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.55",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.2.9",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-98930",
      "aliases": [
        "CVE-2026-98930"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "6cddd432e3da5e25eccbc13844d03c871674a62e"
                },
                {
                  "fixed": "3bd77c59576b1d447fd56cc689ae9523a334b924"
                },
                {
                  "fixed": "a379ac504fcb8c6fc2aa36203f5489b9581eb2e0"
                },
                {
                  "fixed": "d0e3bf633f0585a0c2c2105ea7723777d764fae5"
                },
                {
                  "fixed": "d343407b728a80b74be3c24b59f15e60289ea527"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98930.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "4.0.0"
                },
                {
                  "fixed": "6.12.112"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.55"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.2.9"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98930.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:52.956858075Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/3bd77c59576b1d447fd56cc689ae9523a334b924",
        "https://git.kernel.org/stable/c/a379ac504fcb8c6fc2aa36203f5489b9581eb2e0",
        "https://git.kernel.org/stable/c/d0e3bf633f0585a0c2c2105ea7723777d764fae5",
        "https://git.kernel.org/stable/c/d343407b728a80b74be3c24b59f15e60289ea527",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98930.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-98930",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98930.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-98930",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 521866,
  "published_at": "2026-10-23T12:08:17.513+00:00"
}