From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [master][PATCH 1/3] busybox: fix CVE-2026-38752 To: openembedded-core@lists.openembedded.org From: "Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)" X-Originating-Location: Mumbai, Maharashtra, IN (151.186.177.21) X-Originating-Platform: Windows Edge 157 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Thu, 19 Nov 2026 04:08:59 -0800 References: <20261105073452.890881-1-dkelaiya@cisco.com> In-Reply-To: Message-ID: <966833.1795090139326132224@lists.openembedded.org> Content-Type: multipart/alternative; boundary="ckuZPrwHxhDlW2FYSfBf" List-Id: X-Webhook-Received: from 45-33-107-173.ip.linodeusercontent.com [45.33.107.173] by lin-tor-korg-lkml-alma10-1 with HTTPS for ; Thu, 19 Nov 2026 12:09:07 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/250664 --ckuZPrwHxhDlW2FYSfBf Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Paul, Thanks for the feedback. I checked the downstream package sources. All three June patches are carried by: * Debian BusyBox 1:1.38.0-3 [1]. * Ubuntu 26.10 BusyBox 1:1.38.0-3ubuntu4 , inherited from Debian [2]. * openSUSE Factory, where they were added on 26 August [3]. For CVE-2026-38752, the researcher also published a reproducer and selected ASan/GDB results [4]. Your point about the threat model is fair. For the AWK and shell recursion cases, I have not established a security impact beyond the capabilities already available to an attacker supplying executable scripts. There is also a completeness concern with CVE-2026-38753. During the upstream discussion, the author acknowledged that the original patch was too narrow and planned a broader fix [5]. The downstream packages still carry that original implementation. I=E2=80=99ll reassess the security impact and completeness of these fixes before following up on the series. [1] https://sources.debian.org/data/main/b/busybox/1%3A1.38.0-3/debian/patc= hes/series ( https://sources.debian.org/data/main/b/busybox/1%3A1.38.0-3/de= bian/patches/series ) [2] [ubuntu/stonking-proposed] busybox 1:1.38.0-3ubuntu1 (Accepted) ( https= ://lists.ubuntu.com/archives/stonking-changes/2026-August/005912.html ) [3] https://api.opensuse.org/public/source/openSUSE:Factory/busybox/busybox= .spec?rev=3D99 ( https://api.opensuse.org/public/source/openSUSE:Factory/bu= sybox/busybox.spec?rev=3D99 ) [4] https://hy38.github.io/cves/cve-2026-38752-busybox-awk-recursion-stack-= overflow/ ( https://hy38.github.io/cves/cve-2026-38752-busybox-awk-recursio= n-stack-overflow/ ) [5] https://lists.busybox.net/pipermail/busybox/2026-July/092395.html ( htt= ps://lists.busybox.net/pipermail/busybox/2026-July/092395.html ) Regards, Darsh On Tue, Nov 17, 2026 at 03:30 PM, Paul Barker wrote: >=20 > On Thu Nov 5, 2026 at 7:34 AM GMT, Darsh Kelaiya -X (dkelaiya - E > INFOCHIPS PRIVATE LIMITED at Cisco) wrote: >=20 >> From: Darsh Kelaiya >>=20 >> This patch applies the upstream fix shown in [1]. >> The advisory identifying the fix is referenced in [2]. >>=20 >> [1] https://lists.busybox.net/pipermail/busybox/2026-June/092351.html >> [2] https://nvd.nist.gov/vuln/detail/cve-2026-38752 >>=20 >> Signed-off-by: Darsh Kelaiya >=20 > Hi Darsh, >=20 > The patches here have been submitted to busybox but have not received > any upstream review. Can you point to any evidence that these are good, > e.g. other distros taking these patches? >=20 > TBH I wonder how this is even a CVE issue. As busybox isn't a CNA, and > their patch review process is known to be slow, it's very easy for > someone to just file nonsense CVE reports. >=20 > A stack overflow in the evaluate() function (editors/awk.c) of > BusyBox commit 371fe9 allows attackers to cause a Denial of Service > (DoS) via supplying a crafted AWK script. >=20 > If you can supply your own AWK script, you could just run: >=20 > BEGIN { while (1) print "looping..." } >=20 > Or some other misbehaviour. Bug, yes. Security bug? I don't see how. >=20 > Please step back and do some analysis, I don't think trying to play > whack-a-mole on every CVE report is sustainable. >=20 > Best regards, >=20 > -- > Paul Barker --ckuZPrwHxhDlW2FYSfBf Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Hi Paul,

Thanks for the feedback. I checked the downstream package sources.=
All three June patches are carried by:

  • Debian BusyBox 1:1.38.0-3 [1].
  • Ubuntu 26.10 BusyBox 1:1.38.0-3ubuntu4 , inherited f= rom Debian [2].
  • openSUSE Factory, where they were added on 26 August [3].<= /li>

For CVE-2026-38752, the researcher also published a reproducer and=
selected ASan/GDB results [4].

Your point about the threat model is fair. For the AWK and shell
recursion cases, I have not established a security impact = beyond the
capabilities already available to an attacker = supplying executable
scripts.

There is also a completeness concern with CVE-2026-38753. During t= he
upstream discussion, the author acknowledged that the = original patch
was too narrow and planned a broader fix [= 5]. The downstream packages
still carry that original imp= lementation.

I’ll reassess the security impact and complet= eness of these fixes
before following up on the series.

[1] https://sources.de= bian.org/data/main/b/busybox/1%3A1.38.0-3/debian/patches/series
[2] [ubuntu/stonking-proposed] = busybox 1:1.38.0-3ubuntu1 (Accepted)
[3] https://api.opensuse.org/public/source/openSUS= E:Factory/busybox/busybox.spec?rev=3D99
[4] https://hy38.github.io/cves= /cve-2026-38752-busybox-awk-recursion-stack-overflow/<= /a>
[5]
https://lists.busybox.net/pi= permail/busybox/2026-July/092395.html

Regards,
Darsh

On Tue, Nov 17, 2026 at 03:30 PM, Paul Barker wrote:
On Thu Nov 5, 2026 at 7:34 AM GMT, Darsh Kelaiya -X (dkelaiya -= E INFOCHIPS PRIVATE LIMITED at Cisco) wrote:
From: Darsh Kelaiya <dkelaiya@cisco.com>

This = patch applies the upstream fix shown in [1].
The advisory identifying = the fix is referenced in [2].

[1] https://lists.busybox.net/pipermail/busybox/2026-June/092351.html
[2]
https://nvd.nist.gov/vuln/detail/cve-2026-3= 8752

Signed-off-by: Darsh Kelaiya <dkelaiya@cisco.com>=
Hi Darsh,

The patches here have been submitted to busybox but ha= ve not received
any upstream review. Can you point to any evidence tha= t these are good,
e.g. other distros taking these patches?

= TBH I wonder how this is even a CVE issue. As busybox isn't a CNA, and
their patch review process is known to be slow, it's very easy for
so= meone to just file nonsense CVE reports.

A stack overflow in the= evaluate() function (editors/awk.c) of
BusyBox commit 371fe9 allows a= ttackers to cause a Denial of Service
(DoS) via supplying a crafted AW= K script.

If you can supply your own AWK script, you could just = run:

BEGIN { while (1) print "looping..." }

Or some o= ther misbehaviour. Bug, yes. Security bug? I don't see how.

Plea= se step back and do some analysis, I don't think trying to play
whack-= a-mole on every CVE report is sustainable.

Best regards,
--
Paul Barker
--ckuZPrwHxhDlW2FYSfBf--