From: "Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)" <dkelaiya@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [master][PATCH 1/3] busybox: fix CVE-2026-38752
Date: Thu, 19 Nov 2026 04:08:59 -0800 [thread overview]
Message-ID: <966833.1795090139326132224@lists.openembedded.org> (raw)
In-Reply-To: <DMXEDBPVHWXK.3PLBST96AJJVE@pbarker.dev>
[-- Attachment #1: Type: text/plain, Size: 3292 bytes --]
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’ll 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/patches/series ( https://sources.debian.org/data/main/b/busybox/1%3A1.38.0-3/debian/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=99 ( https://api.opensuse.org/public/source/openSUSE:Factory/busybox/busybox.spec?rev=99 )
[4] https://hy38.github.io/cves/cve-2026-38752-busybox-awk-recursion-stack-overflow/ ( https://hy38.github.io/cves/cve-2026-38752-busybox-awk-recursion-stack-overflow/ )
[5] https://lists.busybox.net/pipermail/busybox/2026-July/092395.html ( https://lists.busybox.net/pipermail/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-38752
>>
>> Signed-off-by: Darsh Kelaiya <dkelaiya@cisco.com>
>
> Hi Darsh,
>
> 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?
>
> 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.
>
> 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.
>
> If you can supply your own AWK script, you could just run:
>
> BEGIN { while (1) print "looping..." }
>
> Or some other misbehaviour. Bug, yes. Security bug? I don't see how.
>
> Please 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
[-- Attachment #2: Type: text/html, Size: 4301 bytes --]
prev parent reply other threads:[~2026-11-19 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 7:34 [OE-core][master][PATCH 1/3] busybox: fix CVE-2026-38752 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-05 7:34 ` [OE-core][master][PATCH 2/3] busybox: fix CVE-2026-38753 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-05 7:34 ` [OE-core][master][PATCH 3/3] busybox: fix CVE-2026-38755 Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-11-17 10:00 ` [OE-core][master][PATCH 1/3] busybox: fix CVE-2026-38752 Paul Barker
2026-11-19 12:08 ` Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at Cisco) [this message]
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=966833.1795090139326132224@lists.openembedded.org \
--to=dkelaiya@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.