Описание
Security update for kubevirt1.8
This update for kubevirt1.8 fixes the following issues:
- CVE-2026-56854,CVE-2026-56855,CVE-2026-78662: golang.org/x/crypto/ssh: authentication bypass and deadlocks in the
crypto/sshlibrary (bsc#1278574). - CVE-2026-78659: golang.org/x/net/http2: HTTP/2 server memory exhaustion due to
Trailerheaders (bsc#1286984). - CVE-2026-78660: golang.org/x/net/http2: HTTP/2 transport accepts malformed framing-related headers (bsc#1287039).
- CVE-2026-78663: golang.org/x/net/http2: double flow control refund on HTTP/2 server streams (bsc#1287143).
- CVE-2026-78669: golang.org/x/net/http2: excessive CPU consumption from repeated initial window changes (bsc#1285255).
- CVE-2026-84303: google.golang.org/grpc: xDS RBAC HTTP filter implementation issue allows for bypass of authorization policies via mixed-case or canonical-case header matches (bsc#1279276).
- CVE-2026-84304: google.golang.org/grpc: heap memory exhaustion via HTTP/2
DATAframe fragmentation (bsc#1279184). - CVE-2026-84445: google.golang.org/grpc: DoS via crash due to missing
:authorityand 'Host' headers in gRPC-Go xDS servers (bsc#1278869). - CVE-2026-97032: golang.org/x/net/http2: HTTP/2 server crash due to
HPACKencoder race (bsc#1287446).
Changes for kubevirt1.8:
- Backport the slow qemu startup fix for virt-handler: when qemu took longer to start than the SyncVMI gRPC timeout, as large-memory VFIO VMs do, virt-handler undefined the Shutoff domain of a Scheduled VMI while startup was still running. The VM then ran as a transient domain and later hotplug failed with libvirt error 55. Defer the deletion for up to 5 minutes (upstream PR 18545, commit b98490cd81).
- Build with Go 1.26: the updated modules require it (go.mod)
- virt-launcher's domain stats collection took libvirt's domain job lock, which an in-flight migration holds on the target, so every stats poll of a migrating VM blocked for the 30 s job timeout and logged "cannot acquire state change lock". Pass the NOWAIT flag so libvirt skips the locked domain instead (upstream release-1.8 commit 4f7eca22df).
- Ship the testing manifests in the tests subpackage on SUSE Linux: they were generated and installed only on Tumbleweed, together with the release manifests, so virt-tests came without the default-config.json, rbac-for-testing.yaml, uploadproxy-nodeport.yaml and disks-images-provider.yaml it needs to run. The release manifests and the manifests subpackage stay Tumbleweed-only.
Список пакетов
openSUSE Leap 16.0
Ссылки
- SUSE Security Ratings
- SUSE Bug 1278574
- SUSE Bug 1278869
- SUSE Bug 1279184
- SUSE Bug 1279276
- SUSE Bug 1285255
- SUSE Bug 1286984
- SUSE Bug 1287039
- SUSE Bug 1287143
- SUSE Bug 1287446
- SUSE CVE CVE-2026-56854 page
- SUSE CVE CVE-2026-56855 page
- SUSE CVE CVE-2026-78659 page
- SUSE CVE CVE-2026-78660 page
- SUSE CVE CVE-2026-78662 page
- SUSE CVE CVE-2026-78663 page
- SUSE CVE CVE-2026-78669 page
- SUSE CVE CVE-2026-84303 page
- SUSE CVE CVE-2026-84304 page
- SUSE CVE CVE-2026-84445 page
Описание
The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. Permissions returned by the PasswordCallback, KeyboardInteractiveCallback, NoClientAuthCallback, and GSSAPIWithMICConfig.AllowLogin callbacks were not validated against the client's remote address, so a source-address restriction set by those callbacks was silently ignored. The check is now applied to the Permissions returned by any authentication callback.
Затронутые продукты
Ссылки
- CVE-2026-56854
- SUSE Bug 1278446
- SUSE Bug 1280553
Описание
Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and tear the connection down instead of buffering and blocking.
Затронутые продукты
Ссылки
- CVE-2026-56855
- SUSE Bug 1278446
- SUSE Bug 1280553
Описание
When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
Затронутые продукты
Ссылки
- CVE-2026-78659
- SUSE Bug 1284768
- SUSE Bug 1286134
Описание
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.
Затронутые продукты
Ссылки
- CVE-2026-78660
- SUSE Bug 1284769
- SUSE Bug 1286129
Описание
Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time, handlePacket drops every packet other than the open confirmation/failure, without blocking and without tearing down the connection.
Затронутые продукты
Ссылки
- CVE-2026-78662
- SUSE Bug 1278446
- SUSE Bug 1280553
Описание
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
Затронутые продукты
Ссылки
- CVE-2026-78663
- SUSE Bug 1284770
- SUSE Bug 1286126
Описание
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
Затронутые продукты
Ссылки
- CVE-2026-78669
- SUSE Bug 1284772
Описание
gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, the xDS RBAC HTTP filter in internal/xds/httpfilter/rbac/rbac.go does not lowercase header matcher names in normalizeHeaderMatcher even though incoming metadata keys are lowercase. A DENY policy using a mixed-case name such as X-Role or User-Agent therefore does not match and fails open, allowing requests that should be rejected. The same case mismatch permits :Scheme or Grpc-Status to evade gRFC A41 validation and prevents Host from being rewritten to :authority. This issue is fixed in version 1.83.1.
Затронутые продукты
Ссылки
- CVE-2026-84303
- SUSE Bug 1278268
- SUSE Bug 1280553
Описание
gRPC-Go is the Go language implementation of gRPC. Prior to 1.83.1, internal/transport/transport.go stores each fragmented HTTP/2 DATA frame as a separate recvMsg in recvBuffer, so millions of one-byte frames can consume disproportionate heap memory even when payload bytes remain within connection and stream flow-control windows. An unauthenticated remote attacker can use concurrent multiplexed streams to exhaust process memory and cause a runtime panic or out-of-memory termination. Receive-buffer compaction is enabled by default and can be controlled temporarily with GRPC_GO_EXPERIMENTAL_ENABLE_RECEIVE_BUFFER_COMPACTION. This issue is fixed in version 1.83.1.
Затронутые продукты
Ссылки
- CVE-2026-84304
- SUSE Bug 1278271
- SUSE Bug 1280553
Описание
gRPC-Go is the Go language implementation of gRPC. Prior to 1.82.2 and 1.83.2, servers created with xds.NewGRPCServer() allow internal/transport/http2_server.go to accept an RPC containing neither the :authority header nor the Host header, while RouteAndProcess in internal/xds/server/routing.go assumes that an authority value exists and indexes the empty slice. A remote client that can complete transport connection establishment can trigger an index-out-of-bounds panic that is not recovered by the per-RPC goroutine and terminates the entire server process. In insecure or ordinary TLS deployments the request can be unauthenticated, while strict mTLS or ALTS deployments require valid transport credentials before the malformed RPC can reach the interceptor. This issue is fixed in versions 1.82.2 and 1.83.2.
Затронутые продукты
Ссылки
- CVE-2026-84445
- SUSE Bug 1278687
- SUSE Bug 1280553
- SUSE Bug 1280617
Описание
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Затронутые продукты
Ссылки
- CVE-2026-97032
- SUSE Bug 1284780
- SUSE Bug 1286108