From: Siddharth <sdoshi@mvista.com>
To: openembedded-core@lists.openembedded.org
Cc: Siddharth Doshi <sdoshi@mvista.com>
Subject: [OE-core][scarthgap][PATCHv2 10/13] vim: Security Fix for CVE-2026-57455
Date: Thu, 23 Jul 2026 14:53:51 +0530 [thread overview]
Message-ID: <20260723092354.54697-10-sdoshi@mvista.com> (raw)
In-Reply-To: <20260723092354.54697-1-sdoshi@mvista.com>
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-57455
[2] https://security-tracker.debian.org/tracker/CVE-2026-57455
Signed-off-by: Siddharth Doshi <sdoshi@mvista.com>
---
.../vim/files/CVE-2026-57455.patch | 72 +++++++++++++++++++
meta/recipes-support/vim/vim.inc | 1 +
2 files changed, 73 insertions(+)
create mode 100644 meta/recipes-support/vim/files/CVE-2026-57455.patch
diff --git a/meta/recipes-support/vim/files/CVE-2026-57455.patch b/meta/recipes-support/vim/files/CVE-2026-57455.patch
new file mode 100644
index 0000000000..722238c794
--- /dev/null
+++ b/meta/recipes-support/vim/files/CVE-2026-57455.patch
@@ -0,0 +1,72 @@
+From 497d2fb19b2af9bccf139bb910e4f91b583e769d Mon Sep 17 00:00:00 2001
+From: Christian Brabandt <cb@256bit.org>
+Date: Sun, 21 Jun 2026 19:20:03 +0000
+Subject: [PATCH 13/17] patch 9.2.0698: [security]: Out-of-bounds write with
+ soundfold()
+
+Problem: [security]: Out-of-bounds write with soundfold()
+ (cipher-creator)
+Solution: Add an abort condition to the for loop to validate the buffer
+ size.
+
+Github Security Advisory:
+https://github.com/vim/vim/security/advisories/GHSA-q8mh-6qm3-25g4
+
+Supported by AI
+
+Signed-off-by: Christian Brabandt <cb@256bit.org>
+
+Upstream-Status: Backport [https://github.com/vim/vim/commit/497f931f85339d175d7f69588dd249e8ccfed41b]
+CVE: CVE-2026-57455
+Signed-off-by: Siddharth Doshi <sdoshi@mvista.com>
+---
+ src/spell.c | 2 +-
+ src/testdir/test_spellfile.vim | 21 +++++++++++++++++++++
+ 2 files changed, 22 insertions(+), 1 deletion(-)
+
+diff --git a/src/spell.c b/src/spell.c
+index 6ef3fa899b..a7909ef46e 100644
+--- a/src/spell.c
++++ b/src/spell.c
+@@ -3273,7 +3273,7 @@ spell_soundfold_sofo(slang_T *slang, char_u *inword, char_u *res)
+ else
+ {
+ // The sl_sal_first[] table contains the translation.
+- for (s = inword; (c = *s) != NUL; ++s)
++ for (s = inword; (c = *s) != NUL && ri < MAXWLEN - 1; ++s)
+ {
+ if (VIM_ISWHITE(c))
+ c = ' ';
+diff --git a/src/testdir/test_spellfile.vim b/src/testdir/test_spellfile.vim
+index e5f8c5778f..d04d024911 100644
+--- a/src/testdir/test_spellfile.vim
++++ b/src/testdir/test_spellfile.vim
+@@ -1193,4 +1193,25 @@ func Test_spell_sug_tree_count_words_overflow()
+ bwipe!
+ endfunc
+
++" A word longer than MAXWLEN must not overflow the soundfold result buffer in
++" the single-byte SOFO branch of spell_soundfold_sofo().
++func Test_soundfold_overflow()
++ let _enc=&enc
++ set enc=latin1
++ call writefile(['SOFOFROM ab', 'SOFOTO xy'], 'Xtest.aff', 'D')
++ call writefile(['1', 'foo'], 'Xtest.dic', 'D')
++ mkspell! Xtest Xtest
++ defer delete('Xtest.latin1.spl')
++ defer delete('Xtest.latin1.sug')
++ setl spelllang=Xtest.latin1.spl spell
++
++ " Before the fix the copy loop wrote one byte per input byte into a
++ " MAXWLEN (254) stack buffer with no upper bound, smashing the stack.
++ let sound = soundfold(repeat('ab', 300))
++ call assert_true(strlen(sound) < 254, 'soundfold result exceeds MAXWLEN')
++
++ set spell& spelllang&
++ let &enc = _enc
++endfunc
++
+ " vim: shiftwidth=2 sts=2 expandtab
+--
+2.44.4
+
diff --git a/meta/recipes-support/vim/vim.inc b/meta/recipes-support/vim/vim.inc
index 567da7be0c..8794f831b0 100644
--- a/meta/recipes-support/vim/vim.inc
+++ b/meta/recipes-support/vim/vim.inc
@@ -45,6 +45,7 @@ SRC_URI = "git://github.com/vim/vim.git;branch=master;protocol=https \
file://CVE-2026-55892.patch \
file://CVE-2026-55895.patch \
file://CVE-2026-57452.patch \
+ file://CVE-2026-57455.patch \
"
PV .= ".1683"
--
2.34.1
next prev parent 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 [OE-core][scarthgap][PATCHv2 01/13] vim: Security Fix for CVE-2026-28422 Siddharth
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 ` Siddharth [this message]
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-10-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