public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/libinstpatch] epel9: Apply a proposed fix for CVE-2026-111136
Date: Sun, 18 Oct 2026 06:22:36 GMT	[thread overview]
Message-ID: <179230455660.1.13900359412360813031.rpms-libinstpatch-5d2b51d9f8e6@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/libinstpatch
Branch : epel9
Commit : 5d2b51d9f8e6cf592381d7d4485e8046da119c9a
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-10-18T07:20:20+01:00
Stats  : +38/-0 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/libinstpatch/c/5d2b51d9f8e6cf592381d7d4485e8046da119c9a?branch=epel9

Log:
Apply a proposed fix for CVE-2026-111136

---
diff --git a/87.patch b/87.patch
new file mode 100644
index 0000000..3cdd3b1
--- /dev/null
+++ b/87.patch
@@ -0,0 +1,31 @@
+From b8a6ff845d3d8a6b947567118d8ea4201759a964 Mon Sep 17 00:00:00 2001
+From: "Benjamin A. Beasley" <code@musicinmybrain.net>
+Date: Sat, 17 Oct 2026 08:48:04 +0100
+Subject: [PATCH] Fix for CVE-2026-111136
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Based on the “short term” fix proposed by @Haind03 (HaiND) in
+https://hackmd.io/@haind-pwn/cve-2026-111136-libinstpatch-sf2-generator-id-oob-write#Fix.
+---
+ libinstpatch/IpatchSF2Gen.c | 6 +++++-
+ 1 file changed, 5 insertions(+), 1 deletion(-)
+
+diff --git a/libinstpatch/IpatchSF2Gen.c b/libinstpatch/IpatchSF2Gen.c
+index 1a4246ff..677a6731 100644
+--- a/libinstpatch/IpatchSF2Gen.c
++++ b/libinstpatch/IpatchSF2Gen.c
+@@ -191,7 +191,11 @@ _ipatch_sf2_gen_deinit (void)
+ gboolean
+ ipatch_sf2_gen_is_valid(guint genid, IpatchSF2GenPropsType propstype)
+ {
+-    if(genid == IPATCH_SF2_GEN_SAMPLE_MODES
++    if(genid >= IPATCH_SF2_GEN_COUNT)
++    {
++        return (FALSE);
++    }
++    else if(genid == IPATCH_SF2_GEN_SAMPLE_MODES
+             && propstype == IPATCH_SF2_GEN_PROPS_INST_GLOBAL)
+     {
+         return (FALSE);

diff --git a/libinstpatch.spec b/libinstpatch.spec
index fffbbca..0ab2cd0 100644
--- a/libinstpatch.spec
+++ b/libinstpatch.spec
@@ -54,6 +54,13 @@ Patch2:          libinstpatch-1.1.6-gtkdoc.patch
 # https://github.com/swami/libinstpatch/pull/77
 # (Fixes CMake 4.0 compatibility.)
 Patch3:          %{forgeurl}/pull/77.patch
+# Fix for CVE-2026-111136
+# https://github.com/swami/libinstpatch/pull/87
+# https://github.com/swami/libinstpatch/issues/86
+# https://www.cve.org/CVERecord?id=CVE-2026-111136
+# https://bugzilla.redhat.com/show_bug.cgi?id=2554067
+# https://bugzilla.redhat.com/show_bug.cgi?id=2554068
+Patch4:          %{forgeurl}/pull/87.patch
 
 BuildRequires:  cmake
 BuildRequires:  gcc

                 reply	other threads:[~2026-10-18  6:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=179230455660.1.13900359412360813031.rpms-libinstpatch-5d2b51d9f8e6@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox