LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23027: LoongArch: KVM: Fix kvm_device leak in kvm_pch_pic_destroy()

In the Linux kernel, the following vulnerability has been resolved: LoongArch: KVM: Fix kvm_device leak in kvm_pch_pic_destroy() In kvm_ioctl_create_device(), kvm_device has allocated memory, kvm_device->destroy() seems to be supposed to free its kvm_device struct, but kvm_pch_pic_destroy() is not currently doing this, that would lead to a memory leak. So, fix it.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in LoongArch KVM virtual machine device cleanup. It may gradually waste kernel memory when the affected virtual interrupt controller device is created and destroyed. The sources do not provide a CVSS score, exploitability assessment, or evidence of active exploitation.

Executive priority

Treat this as a targeted Linux virtualization maintenance item, not a broad emergency. Prioritize LoongArch KVM hosts, especially shared virtualization infrastructure, and fold remediation into normal kernel patch cycles unless vendor guidance raises severity.

Technical view

The bug is in LoongArch KVM: kvm_ioctl_create_device() allocates a kvm_device, but kvm_pch_pic_destroy() did not free that structure during destruction. The upstream fix corrects the missing free path. Impact evidence is limited to memory leakage; no source in the bundle describes privilege escalation, code execution, or data exposure.

Likely exposure

Exposure appears limited to Linux systems using LoongArch KVM functionality with the PCH PIC device path. Generic Linux systems on other architectures, or systems not using this KVM device behavior, are not shown as exposed by the provided sources.

Exploitation context

The bundle marks KEV as false and provides no public exploitation evidence. The issue could matter operationally if repeated device lifecycle activity causes kernel memory pressure, but the sources do not establish practical exploitability or attack prerequisites.

Researcher notes

Evidence supports a missing kvm_device free in kvm_pch_pic_destroy(). The source bundle lacks CVSS, CWE mapping, exploit details, and concrete affected distribution packages. Avoid broader impact claims beyond LoongArch KVM until vendor advisories add context.

Mitigation direction

  • Review vendor kernel advisories for CVE-2026-23027 applicability.
  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Prioritize LoongArch virtualization hosts running KVM workloads.
  • If patching is delayed, monitor affected hosts for abnormal kernel memory growth.

Validation and detection

  • Inventory Linux hosts by architecture, kernel version, and KVM usage.
  • Identify LoongArch systems using KVM device creation paths.
  • Compare deployed kernel builds against vendor guidance and referenced stable commits.
  • Confirm patched kernels include the kvm_pch_pic_destroy() memory leak fix.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2026-23027 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe785dfacf7e7fe94370fa0e8e3ff1bc8fe179831, e785dfacf7e7fe94370fa0e8e3ff1bc8fe179831unaffected
LinuxLinux6.13, 0, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.