Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Siddharth <sdoshi@mvista.com>
To: openembedded-core@lists.openembedded.org
Cc: Siddharth Doshi <sdoshi@mvista.com>
Subject: [OE-core][scarthgap][PATCHv2 01/13] vim: Security Fix for CVE-2026-28422
Date: Thu, 23 Jul 2026 14:53:42 +0530	[thread overview]
Message-ID: <20260723092354.54697-1-sdoshi@mvista.com> (raw)

From: Siddharth Doshi <sdoshi@mvista.com>

Picking patch as per [1], and same patch is mentioned in [2]

References:
[1] https://nvd.nist.gov/vuln/detail/CVE-2026-28422
[2] https://security-tracker.debian.org/tracker/CVE-2026-28422

Signed-off-by: Siddharth Doshi <sdoshi@mvista.com>
---
 .../vim/files/CVE-2026-28422.patch            | 44 +++++++++++++++++++
 meta/recipes-support/vim/vim.inc              |  1 +
 2 files changed, 45 insertions(+)
 create mode 100644 meta/recipes-support/vim/files/CVE-2026-28422.patch

diff --git a/meta/recipes-support/vim/files/CVE-2026-28422.patch b/meta/recipes-support/vim/files/CVE-2026-28422.patch
new file mode 100644
index 0000000000..89f219ccf6
--- /dev/null
+++ b/meta/recipes-support/vim/files/CVE-2026-28422.patch
@@ -0,0 +1,44 @@
+From fcf19885004325f5a52db6bd6893cb5b387799d3 Mon Sep 17 00:00:00 2001
+From: Christian Brabandt <cb@256bit.org>
+Date: Tue, 24 Feb 2026 20:29:20 +0000
+Subject: [PATCH 01/17] patch 9.2.0078: [security]: stack-buffer-overflow in
+ build_stl_str_hl()
+
+Problem:  A stack-buffer-overflow occurs when rendering a statusline
+          with a multi-byte fill character on a very wide terminal.
+          The size check in build_stl_str_hl() uses the cell width
+          rather than the byte length, allowing the subsequent fill
+          loop to write beyond the 4096-byte MAXPATHL buffer
+          (ehdgks0627, un3xploitable).
+Solution: Update the size check to account for the byte length of
+          the fill character (using MB_CHAR2LEN).
+
+Github Advisory:
+https://github.com/vim/vim/security/advisories/GHSA-gmqx-prf2-8mwf
+
+Signed-off-by: Christian Brabandt <cb@256bit.org>
+
+Upstream-Status: Backport [https://github.com/vim/vim/commit/4e5b9e31cb7484ad156fba995fdce3c9b075b5fd]
+CVE: CVE-2026-28422
+Signed-off-by: Siddharth Doshi <sdoshi@mvista.com>
+---
+ src/buffer.c | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/src/buffer.c b/src/buffer.c
+index 0feafc590d..363dd0e04a 100644
+--- a/src/buffer.c
++++ b/src/buffer.c
+@@ -5293,7 +5293,8 @@ build_stl_str_hl(
+ 	}
+ 	width = maxwidth;
+     }
+-    else if (width < maxwidth && outputlen + maxwidth - width + 1 < outlen)
++    else if (width < maxwidth &&
++	    outputlen + (maxwidth - width) * MB_CHAR2LEN(fillchar) + 1 < outlen)
+     {
+ 	// Find how many separators there are, which we will use when
+ 	// figuring out how many groups there are.
+-- 
+2.44.4
+
diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index d69a337b4e..485eedb061 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/recipes-support/vim/vim.inc
@@ -36,6 +36,7 @@ SRC_URI = "git://github.com/vim/vim.git;branch=master;protocol=https \
            file://CVE-2026-52858.patch \
            file://CVE-2026-52859.patch \
            file://CVE-2026-52860.patch \
+           file://CVE-2026-28422.patch \
            "
 
 PV .= ".1683"
-- 
2.34.1



             reply	other threads:[~2026-07-23  9:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  9:23 Siddharth [this message]
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 02/13] vim: Security Fix for CVE-2026-42307 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 03/13] vim: Security Fix for CVE-2026-43961 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 04/13] vim: Security Fix for CVE-2026-47162 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 05/13] vim: Security Fix for CVE-2026-47167 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 06/13] vim: Security Fix for CVE-2026-55693 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 07/13] vim: Security Fix for CVE-2026-55892 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 08/13] vim: Security Fix for CVE-2026-55895 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 09/13] vim: Security Fix for CVE-2026-57452 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 10/13] vim: Security Fix for CVE-2026-57455 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 11/13] vim: Security Fix for CVE-2026-59856 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 12/13] vim: Security Fix for CVE-2026-59857 Siddharth
2026-07-23  9:23 ` [OE-core][scarthgap][PATCHv2 13/13] vim: Security Fix for CVE-2026-59858 Siddharth

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=20260723092354.54697-1-sdoshi@mvista.com \
    --to=sdoshi@mvista.com \
    --cc=openembedded-core@lists.openembedded.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