Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package ignition for openSUSE:Factory 
checked in at 2026-05-29 18:04:21
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/ignition (Old)
 and      /work/SRC/openSUSE:Factory/.ignition.new.1937 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "ignition"

Fri May 29 18:04:21 2026 rev:59 rq:1355643 version:2.26.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/ignition/ignition.changes        2026-04-01 
19:55:19.588833090 +0200
+++ /work/SRC/openSUSE:Factory/.ignition.new.1937/ignition.changes      
2026-05-29 18:04:42.548406473 +0200
@@ -1,0 +2,6 @@
+Thu May 28 12:39:10 UTC 2026 - Ignaz Forster <[email protected]>
+
+- Add CVE-2026-33814.patch
+  * Fixes [bsc#1265751]
+
+-------------------------------------------------------------------

New:
----
  CVE-2026-33814.patch

----------(New B)----------
  New:
- Add CVE-2026-33814.patch
  * Fixes [bsc#1265751]
----------(New E)----------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ ignition.spec ++++++
--- /var/tmp/diff_new_pack.sRPRIz/_old  2026-05-29 18:04:44.068469344 +0200
+++ /var/tmp/diff_new_pack.sRPRIz/_new  2026-05-29 18:04:44.072469509 +0200
@@ -44,6 +44,7 @@
 Patch3:         0003-Move-the-GPT-header-on-resized-disks.patch
 Patch4:         0004-Order-ignition-disks.service-before-systemd-fsck-roo.patch
 Patch5:         CVE-2026-33186.patch
+Patch6:         CVE-2026-33814.patch
 BuildRequires:  dracut
 BuildRequires:  libblkid-devel
 BuildRequires:  systemd-rpm-macros

++++++ CVE-2026-33814.patch ++++++
>From 24432ec7c0f9e4a7685da29b86ebe6ab852c6486 Mon Sep 17 00:00:00 2001
From: Nicholas S. Husin <[email protected]>
Date: Tue, 31 Mar 2026 15:02:11 -0400
Subject: [PATCH] net/http/internal/http2: prevent hanging Transport due to bad 
SETTINGS frame

When processing SETTINGS frame, Transport currently only checks if the
frame is valid for SETTINGS_ENABLE_CONNECT_PROTOCOL. As a result, a
SETTINGS_MAX_FRAME_SIZE with the invalid value of 0 is erroneously
accepted. This will then result in Transport being stuck in an infinite
loop writing CONTINUATION frames.

This CL fixes the issue by ensuring that SETTINGS frame are always
validated, regardless of the SETTINGS parameter.

Fixes #78476
Fixes CVE-2026-33814

Change-Id: I8b6219431e87454d34bca738fbcb59b66a6a6964
---

diff --git a/vendor/golang.org/x/net/http2/transport.go 
b/vendor/golang.org/x/net/http2/transport.go
index 36423b2..2b04bed 100644
--- a/vendor/golang.org/x/net/http2/transport.go
+++ b/vendor/golang.org/x/net/http2/transport.go
@@ -2836,6 +2836,9 @@
 
        var seenMaxConcurrentStreams bool
        err := f.ForeachSetting(func(s Setting) error {
+               if err := s.Valid(); err != nil {
+                       return err
+               }
                switch s.ID {
                case SettingMaxFrameSize:
                        cc.maxFrameSize = s.Val
@@ -2867,9 +2870,6 @@
                        cc.henc.SetMaxDynamicTableSize(s.Val)
                        cc.peerMaxHeaderTableSize = s.Val
                case SettingEnableConnectProtocol:
-                       if err := s.Valid(); err != nil {
-                               return err
-                       }
                        // If the peer wants to send us 
SETTINGS_ENABLE_CONNECT_PROTOCOL,
                        // we require that it do so in the first SETTINGS frame.
                        //

Reply via email to