Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

KVM: SVM: Preserve TLB control (i.e. pending TLB flush) on failed VMRUN

No KEV listing collectedCVSS 7.8Fix not stated

Assessment

Severity
Important
CVSS base score
7.8
Impact
Not stated
Exploitation detected
Unknown: not stated by MSRC
Exploitability
Not assessed
Publicly disclosed
Unknown: not stated by MSRC
EPSS · 30-day forecast
No EPSS score collected
Customer action
Required: follow the MSRC remediation guidance
More details
CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Public detection template
No Nuclei template is listed in the current collected catalog
Component
Mariner
Weakness
—
Issued by
Linux
Published
20 Oct 2026 · October 2026
Last revised
20 Nov 2026Information published.
CVSS 3.1 base metricsRed raises the risk · green lowers it
Attack vector
LocalAV:L
Attack complexity
HighAC:H
Privileges required
LowPR:L
User interaction
NoneUI:N
Scope
ChangedS:C
Confidentiality
HighC:H
Integrity
HighI:H
Availability
HighA:H

Updates that fix it

0 KBs

No KB listed

No KB update is listed in the collected MSRC record. Check the MSRC advisory for product releases and other remedies.

Affected products

Open Source Software
4 affected products
  • azl3 kernel 6.6.157.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.161.1-1 on Azure Linux 3.0
  • azl4 kernel 6.18.57-1.12.azl4 on Azure Linux 4.0

What changed

  1. Affected products: azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0, azl3 kernel 6.6.161.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0, azl3 kernel 6.6.161.1-1 on Azure Linux 3.0, azl4 kernel 6.18.57-1.12.azl4 on Azure Linux 4.0
  2. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  3. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  4. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  5. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  6. Affected products: azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0, azl3 kernel 6.6.161.1-1 on Azure Linux 3.0
  7. Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  8. Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  9. Affected products: azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
  10. Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → Unknown: not stated by MSRC · Exploitation detected: Not reported by MSRC → Unknown: not stated by MSRC
  11. Detection template: Unknown: exploit-code evidence is incomplete or retained → No Nuclei template listed · CISA KEV: Unknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
  12. Detection template: No Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained · CISA KEV: Not listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (48)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 20 Nov 2026 · 08:58:07 UTC Last revised5 Nov 2026 14:51 UTC → 20 Nov 2026 01:13 UTC
  2. 20 Nov 2026 · 08:58:07 UTC Affected productsazl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0, azl3 kernel 6.6.161.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0, azl3 kernel 6.6.161.1-1 on Azure Linux 3.0, azl4 kernel 6.18.57-1.12.azl4 on Azure Linux 4.0
  3. 13 Nov 2026 · 12:10:20 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  4. 13 Nov 2026 · 12:10:20 UTC Source coverage: public-exploit-codeIncomplete → Current
  5. 13 Nov 2026 · 12:10:20 UTC Source coverage: first-epssIncomplete → Current
  6. 13 Nov 2026 · 12:10:20 UTC Source coverage: msrc-cvrfIncomplete → Current
  7. 13 Nov 2026 · 11:07:20 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  8. 13 Nov 2026 · 11:07:20 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  9. 13 Nov 2026 · 11:07:20 UTC Source coverage: first-epssCurrent → Incomplete
  10. 13 Nov 2026 · 11:07:20 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  11. 6 Nov 2026 · 17:32:22 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  12. 6 Nov 2026 · 17:32:22 UTC Source coverage: public-exploit-codeIncomplete → Current
  13. 6 Nov 2026 · 17:32:22 UTC Source coverage: first-epssIncomplete → Current
  14. 6 Nov 2026 · 17:32:22 UTC Source coverage: msrc-cvrfIncomplete → Current
  15. 6 Nov 2026 · 16:31:02 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  16. 6 Nov 2026 · 16:31:02 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  17. 6 Nov 2026 · 16:31:02 UTC Source coverage: first-epssCurrent → Incomplete
  18. 6 Nov 2026 · 16:31:02 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  19. 6 Nov 2026 · 09:07:49 UTC Last revised1 Nov 2026 14:51 UTC → 5 Nov 2026 14:51 UTC
  20. 6 Nov 2026 · 09:07:49 UTC Affected productsazl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0, azl3 kernel 6.6.161.1-1 on Azure Linux 3.0
  21. 2 Nov 2026 · 17:30:39 UTC Public detection templateUnknown: detection-template evidence is incomplete or retained → No Nuclei template listed
  22. 2 Nov 2026 · 17:30:39 UTC Source coverage: public-exploit-codeIncomplete → Current
  23. 2 Nov 2026 · 17:30:39 UTC Source coverage: first-epssIncomplete → Current
  24. 2 Nov 2026 · 17:30:39 UTC Source coverage: msrc-cvrfIncomplete → Current
  25. 2 Nov 2026 · 16:27:39 UTC Public detection templateNo Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
  26. 2 Nov 2026 · 16:27:39 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  27. 2 Nov 2026 · 16:27:39 UTC Source coverage: first-epssCurrent → Incomplete
  28. 2 Nov 2026 · 16:27:39 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  29. 2 Nov 2026 · 09:04:36 UTC Last revised21 Oct 2026 18:41 UTC → 1 Nov 2026 14:51 UTC
  30. 2 Nov 2026 · 09:04:36 UTC Affected productsazl3 kernel 6.6.157.1-1 on Azure Linux 3.0 → azl3 kernel 6.6.157.1-1 on Azure Linux 3.0, azl3 kernel 6.6.159.1-1 on Azure Linux 3.0
  31. 29 Oct 2026 · 20:19:26 UTC Public detection templateNo Nuclei template listed
  32. 29 Oct 2026 · 20:19:26 UTC EPSSNot scored → No EPSS score collected
  33. 29 Oct 2026 · 20:19:26 UTC Customer actionRequired: apply the update → Required: follow the MSRC remediation guidance
  34. 29 Oct 2026 · 20:19:26 UTC Publicly disclosedNo → Unknown: not stated by MSRC
  35. 29 Oct 2026 · 20:19:26 UTC Exploitation detectedNot reported by MSRC → Unknown: not stated by MSRC
  36. 23 Oct 2026 · 09:33:49 UTC Public exploit codeUnknown: exploit-code evidence is incomplete or retained → No Nuclei template listed
  37. 23 Oct 2026 · 09:33:49 UTC CISA KEVUnknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
  38. 23 Oct 2026 · 09:33:49 UTC Source coverage: public-exploit-codeIncomplete → Current
  39. 23 Oct 2026 · 09:33:49 UTC Source coverage: first-epssIncomplete → Current
  40. 23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
  41. 23 Oct 2026 · 09:33:49 UTC Source coverage: msrc-cvrfIncomplete → Current
  42. 23 Oct 2026 · 08:31:50 UTC Public exploit codeNo Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained
  43. 23 Oct 2026 · 08:31:50 UTC CISA KEVNot listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
  44. 23 Oct 2026 · 08:31:50 UTC Source coverage: public-exploit-codeCurrent → Incomplete
  45. 23 Oct 2026 · 08:31:50 UTC Source coverage: first-epssCurrent → Incomplete
  46. 23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete
  47. 23 Oct 2026 · 08:31:50 UTC Source coverage: msrc-cvrfCurrent → Incomplete
  48. 21 Oct 2026 · 20:45:25 UTC Last revised20 Oct 2026 14:44 UTC → 21 Oct 2026 18:41 UTC

Explore global source statements, affected packages and advisory history for CVE-2026-98715. The catalog has a separate collection scope from Microsoft release records.

More advisories, affected versions and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-98715

Published

KVM: SVM: Preserve TLB control (i.e. pending TLB flush) on failed VMRUN

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Preserve TLB control (i.e. pending TLB flush) on failed VMRUN Don't reset the VMCB's TLB control back to "do nothing" on a failed VMRUN, as empirical testing shows that the CPU performs the requested TLB flush if and only if VMRUN is successful, i.e. clearing TLB control on a failed VMRUN effectively drops a TLB flush. Explicitly track the need to flush all ASIDs on a per-CPU basis, as the ASID reuse condition is tied to the pCPU, not to the vCPU. As a bonus, this also obviates the need to avoid clobbering FLUSH_ALL_ASID with TLB_CONTROL_FLUSH_ASID, e.g. in svm_flush_tlb_asid(). Deliberately don't bother saving/restoring the "old" tlb_ctl on failure, in quotes because it's not exactly the old tlb_ctl, it's the tlb_ctl from after pre_svm_run(), but before updating tlb_ctl for flush_all_asids. If VMRUN fails and TLB_CONTROL_FLUSH_ALL_ASID is forced, then the next successful run of the VMCB *may* unnecessarily flush all ASIDs, which strictly speaking could result in noisy neighbor issues. However, the fact that new_asid() is already guest-triggerable, because of KVM's flawed behavior of clearing the ASID on emulated INIT, means that a guest can already trigger a flush of all ASIDs at roughly the same rate. And once KVM stops clobbering the ASID on emulated INIT, *or* assigns a static ASID to each vCPU, this flaw goes away.

Source published
18 Oct 2026 15:46:47 UTC
Source modified
10 Nov 2026 18:15:18 UTC
Saved here
10 Nov 2026 20:21:22 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 00:41 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current