{"schema":"vulnpedia.research/1","cve":"CVE-2026-98399","generated":"2026-10-26T13:52:32.101Z","references":[{"url":"https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2","tags":[],"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","origins":[{"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","url":"https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2"},{"source":"nvd","sourceId":"CVE-2026-98399","modified":"2026-10-19T10:18:44.700","url":"https://git.kernel.org/stable/c/41647864e62b28388ecccc23a82f0e0a091f4ef2"}]},{"url":"https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb","tags":[],"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","origins":[{"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","url":"https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb"},{"source":"nvd","sourceId":"CVE-2026-98399","modified":"2026-10-19T10:18:44.700","url":"https://git.kernel.org/stable/c/aed56fa3108b7095e6a048e134981506c056a6cb"}]},{"url":"https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d","tags":[],"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","origins":[{"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","url":"https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d"},{"source":"nvd","sourceId":"CVE-2026-98399","modified":"2026-10-19T10:18:44.700","url":"https://git.kernel.org/stable/c/8d7988e8116c3d29d9e02ca9d37ee84577643f2d"}]},{"url":"https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262","tags":[],"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","origins":[{"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","url":"https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262"},{"source":"nvd","sourceId":"CVE-2026-98399","modified":"2026-10-19T10:18:44.700","url":"https://git.kernel.org/stable/c/280ff19853440d59e031cd8fe161e81305721262"}]},{"url":"https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e","tags":[],"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","origins":[{"source":"mitre","sourceId":"Linux","modified":"2026-10-19T09:18:52.784Z","url":"https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e"},{"source":"nvd","sourceId":"CVE-2026-98399","modified":"2026-10-19T10:18:44.700","url":"https://git.kernel.org/stable/c/37f61b71cbc0caefc01022a19ee56fc2510e2e6e"}]},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","tags":["vendor-advisory"],"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"url":"https://access.redhat.com/security/cve/CVE-2026-98399","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://access.redhat.com/security/cve/CVE-2026-98399"}]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2552222","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2552222"}]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98399","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://www.cve.org/CVERecord?id=CVE-2026-98399"}]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98399","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98399"}]},{"url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-98399.mbox","tags":["vendor-reference"],"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-98399.mbox"}]},{"source":"euvd","sourceId":"EUVD-2026-101048","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-101048","tags":["ADVISORY"],"origins":[{"source":"euvd","sourceId":"EUVD-2026-101048","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-101048"}]}],"packages":[],"pocCandidates":[],"cataloguedPoc":[],"vendorStatements":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel","product":"kernel as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel-64k-debug-modules-extra","product":"kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-64k-debug-modules-extra","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel-debug-core","product":"kernel-debug-core as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-debug-core","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel-doc","product":"kernel-doc as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-doc","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel-rt-64k-debug","product":"kernel-rt-64k-debug as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-64k-debug","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel-rt-64k-modules-extra","product":"kernel-rt-64k-modules-extra as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-64k-modules-extra","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel-rt-debug-modules-extra","product":"kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-debug-modules-extra","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel-uki-virt","product":"kernel-uki-virt as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-uki-virt","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_10:kernel.src","product":"kernel.src as a component of Red Hat Enterprise Linux 10","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_6:kernel-debug","product":"kernel-debug as a component of Red Hat Enterprise Linux 6","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"no_fix_planned","details":"Out of support scope"}],"purl":"pkg:rpm/redhat/kernel-debug","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_6:perf","product":"perf as a component of Red Hat Enterprise Linux 6","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"no_fix_planned","details":"Out of support scope"}],"purl":"pkg:rpm/redhat/perf","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_7:kernel-doc","product":"kernel-doc as a component of Red Hat Enterprise Linux 7","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-doc","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_7:kernel-rt-doc","product":"kernel-rt-doc as a component of Red Hat Enterprise Linux 7","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-doc","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_7:kernel.src","product":"kernel.src as a component of Red Hat Enterprise Linux 7","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel?arch=src","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_8:kernel-debug","product":"kernel-debug as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-debug","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_8:kernel-ipaclones-internal","product":"kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-ipaclones-internal","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_8:kernel-rt-debug-devel","product":"kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-debug-devel","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_8:kernel-rt-modules-internal","product":"kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-modules-internal","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_8:kernel-zfcpdump-devel","product":"kernel-zfcpdump-devel as a component of Red Hat Enterprise Linux 8","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-zfcpdump-devel","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-64k","product":"kernel-64k as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-64k","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-64k-debug-modules-internal","product":"kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-64k-debug-modules-internal","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-abi-stablelists","product":"kernel-abi-stablelists as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-abi-stablelists","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-debug-modules-extra","product":"kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-debug-modules-extra","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-ipaclones-internal","product":"kernel-ipaclones-internal as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-ipaclones-internal","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-rt-64k-debug","product":"kernel-rt-64k-debug as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-64k-debug","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-rt-64k-debug-modules-partner","product":"kernel-rt-64k-debug-modules-partner as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-64k-debug-modules-partner","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-rt-64k-modules-partner","product":"kernel-rt-64k-modules-partner as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-64k-modules-partner","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-rt-debug-modules-extra","product":"kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-debug-modules-extra","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-rt-modules-internal","product":"kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-rt-modules-internal","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-uki-virt-addons","product":"kernel-uki-virt-addons as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-uki-virt-addons","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_enterprise_linux_9:kernel-zfcpdump-modules-partner","product":"kernel-zfcpdump-modules-partner as a component of Red Hat Enterprise Linux 9","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:rpm/redhat/kernel-zfcpdump-modules-partner","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]},{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json","productId":"red_hat_openshift_container_platform_4:openshift/ose-rhel-coreos-9","product":"openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4","status":"known_affected","remediations":[{"category":"workaround","details":"On affected s390 systems booted without an IPL parameter block (for example via HMC FTP boot or QEMU direct kernel boot), using kdump instead of the stand-alone dumper avoids the vulnerable code path, because kdump passes the re-IPL parameter block through os_info rather than through the lowcore IPL parameter block address and checksum. For environments that rely on the stand-alone dumper, booting the system with a valid IPL parameter block also avoids the NULL dereference path, as valid re-IPL parameter blocks are handled as before. Fixes for the affected Red Hat kernel streams are currently deferred and no fixed package version is available at this time."},{"category":"none_available","details":"Fix deferred"}],"purl":"pkg:oci/ose-rhel-coreos-9?repository_url=registry.redhat.io/openshift/ose-rhel-coreos-9","origins":[{"source":"redhat","sourceId":"CVE-2026-98399","modified":"2026-10-18T08:29:19+00:00","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-98399.json"}]}],"vendorCoverage":{"total":277,"shown":32,"omitted":245,"source":"redhat"}}