In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: Fix race in _destroy_pages_crste()
Use READ_ONCE() in _destroy_pages_crste() to read the crste, avoid dereferencing the pointer multiple times.
Also known asEUVD-2026-103563 (ENISA EUVD) · GHSA-rw83-2w75-m53r (GitHub Security Advisories)Source: ENISA EUVD
A fix is available — apply it.
In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: Fix race in _destroy_pages_crste()
Use READ_ONCE() in _destroy_pages_crste() to read the crste, avoid dereferencing the pointer multiple times.
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
October 18, 2026
October 19, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | linux-tools-realtime-hwe-26.04-edge (7.0.0-43.43.1) @ resolute | 2026-11-18 | ubuntu |
| ubuntu | linux-tools-oem-7.0 (7.0.0-1017.17) @ resolute | 2026-11-18 | ubuntu |
| ubuntu | linux-virtual-hwe-26.04-edge (7.0.0-42.42) @ resolute | 2026-11-18 | ubuntu |
| ubuntu | linux-tools-raspi-realtime-7.0 (7.0.0-1023.23) @ resolute | 2026-11-18 | ubuntu |
| ubuntu | linux-tools-azure-lts-26.04 (7.0.0-1020.21) @ resolute | 2026-11-18 | ubuntu |
| linux | Kernel @ 7.2.9 (fixes >=7.0.0) | — | osv |
These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| linux | 6.12.100-1 ... 7.2~rc7-1~exp1 (184 versions) |
| — |
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-98649
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.