Security readout for executives and security teams
Plain-English summary
A flaw in Linux KVM can cause use-after-free memory corruption when privileged virtualization software improperly removes a guest-memory-file flag from an existing memory slot. A local user with KVM access could potentially compromise confidentiality, integrity, or availability. Systems not using KVM guest_memfd are less likely to be exposed.
Executive priority
Prioritize patch assessment for multi-tenant or shared KVM hosts because successful memory corruption could affect the host security boundary. Treat isolated systems without KVM or guest_memfd use as lower urgency after validation. The incomplete version-range data makes vendor package confirmation essential.
Technical view
KVM allowed KVM_MEM_GUEST_MEMFD to be cleared on an existing bound memslot, despite not supporting that transition. The stale guest_memfd binding can later reach freed memslot memory in kvm_gmem_release, producing a slab use-after-free. The documented correction rejects the unsupported flag change.
Likely exposure
Exposure is concentrated on Linux virtualization hosts where local, lower-privileged processes can access KVM and create or modify guest_memfd-backed memory slots. The supplied version metadata lists Linux 6.8, 6.12.64, 6.18.3, and 6.19 as affected, but does not clearly define complete vulnerable ranges.
Exploitation context
The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with potentially high confidentiality, integrity, and availability impact. The source bundle reports a KASAN reproducer, but no CISA KEV listing or evidence of active exploitation. A reproducible crash is not proof of reliable privilege escalation.
Researcher notes
The demonstrated fault is a write-after-free in kvm_gmem_release after a FLAGS_ONLY memslot update clears KVM_MEM_GUEST_MEMFD without unbinding. The report notes that merely unbinding would address the immediate symptom, while rejecting unsupported toggling corrects the invalid state transition. No CWE classification was supplied.
Mitigation direction
- Identify KVM hosts using guest_memfd-backed virtual-machine memory.
- Apply distribution-supported kernel updates containing the referenced upstream correction.
- Reboot hosts into the corrected kernel after normal change-control testing.
- Restrict KVM device access to trusted virtualization services and administrators.
- Check vendor advisories for precise affected and fixed package versions.
Validation and detection
- Record the running kernel version and distribution package release on every KVM host.
- Confirm the installed source or vendor package includes the referenced corrective commit.
- Verify hosts rebooted into the updated kernel, not merely installed it.
- Review permissions on KVM device nodes and virtualization service accounts.
- Use approved regression tests to confirm guest_memfd workloads remain operational.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2025-68810 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/89dbbe6ff323fc34659621a577fe0af913f47386CVE reference, Linux
- https://git.kernel.org/stable/c/cb51bef465d8ec60a968507330e01020e35dc127CVE reference, Linux
- https://git.kernel.org/stable/c/9935df5333aa503a18de5071f53762b65c783c4cCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.