Patch tracker / CVE reference / CVE-2026-64600

CVE-2026-64600

A security vulnerability affecting azl3 kernel 6.6.144.1-1 on Azure Linux 3.0.

High

High severity Microsoft vulnerability, CVSS 7.8.

How to fix CVE-2026-64600 What the press says Change history Admin questions

Risk summary

CVSS base

7.8

Severity

High

Actively exploited

Not listed

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS under 1%.

No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Updated July 26, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion and rich prompt for CVE-2026-64600

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-64600 (source: https://senserva.com/cve/CVE-2026-64600.html, data from MSRC, CISA KEV and NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-64600: High severity Microsoft vulnerability, CVSS 7.8
- xfs: resample the data fork mapping after cycling ILOCK
- Actively exploited (CISA KEV): no
- Affected: azl3 kernel 6.6.144.1-1 on Azure Linux 3.0
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for CVE-2026-64600

Published

2026-07-24

Last revised

2026-07-24

Changes tracked

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

What the press says about CVE-2026-64600

Trusted-source coverage, pulled live from their own feeds.

“RefluXFS: A Linux Kernel Local Privilege Escalation to Root in XFS (CVE-2026-64600)” Qualys, 2026-07-22

How to fix CVE-2026-64600

Apply the latest Microsoft security update for the affected product. Most environments deliver it automatically through Intune update rings, Windows Update for Business, Windows Autopatch, or WSUS; for a manual install, download from the Microsoft Update Catalog. The MSRC advisory lists the exact patched build per product.

Microsoft MSRC advisory NVD detail

Affected products

azl3 kernel 6.6.144.1-1 on Azure Linux 3.0

Common questions about CVE-2026-64600

Is CVE-2026-64600 actively exploited?

It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. That can change: unexploited CVEs regularly get weaponized months after disclosure, which is why patching on your normal cadence matters.

What fixes CVE-2026-64600?

Microsoft ships the fix in its security updates. Apply the latest cumulative or security update for the affected product through Windows Update, Intune, Windows Update for Business, or the Microsoft Update Catalog, and see the MSRC advisory below for the exact build.

Which products are affected by CVE-2026-64600?

azl3 kernel 6.6.144.1-1 on Azure Linux 3.0.

Can I ask my own AI about CVE-2026-64600?

Yes. This page includes a free, ready-to-paste AI prompt with CVE-2026-64600's key facts: severity, CVSS, CISA KEV status, and the affected products. Copy it into Claude, ChatGPT, or Copilot for a triage plan.

Authoritative references

CVE record NVD detail Microsoft MSRC

Every Microsoft CVE and the patches that fix it, ranked by real-world risk: the Microsoft Patch Tracker. The full searchable CVE reference: CVE and vulnerability management.