Bug 2543219 (CVE-2026-102623) - CVE-2026-102623 kubevirt: kubevirt: virt-controller nil-pointer dereference via malformed ephemeral volume
Summary: CVE-2026-102623 kubevirt: kubevirt: virt-controller nil-pointer dereference v...
Keywords:
Status: NEW
Alias: CVE-2026-102623
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-29 14:45 UTC by OSIDB Bzimport
Modified: 2026-09-29 14:48 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-29 14:45:36 UTC
A flaw was found in KubeVirt's virt-controller. A namespace tenant with permission to create VirtualMachineInstance resources can submit a VMI with an empty ephemeral volume specification (ephemeral: {}). The admission webhook validates that the Ephemeral field is non-nil but does not check the inner PersistentVolumeClaim pointer, which defaults to nil as an optional field. When virt-controller processes this VMI, the rendervolumes code dereferences the nil PersistentVolumeClaim pointer, causing a panic. Because the Kubernetes crash handler re-panics by default and the malformed VMI persists in etcd, the controller enters a permanent crash loop, blocking all VM lifecycle operations cluster-wide until an administrator manually deletes the offending VMI.


Note You need to log in before you can comment on or make changes to this bug.