From: "Paul Barker" <paul@pbarker.dev>
To: "Darsh Kelaiya -X (dkelaiya - E INFOCHIPS PRIVATE LIMITED at
Cisco)" <dkelaiya@cisco.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][master][PATCH 1/3] busybox: fix CVE-2026-38752
Date: Tue, 17 Nov 2026 10:00:53 +0000 [thread overview]
Message-ID: <DMXEDBPVHWXK.3PLBST96AJJVE@pbarker.dev> (raw)
In-Reply-To: <20261105073452.890881-1-dkelaiya@cisco.com>
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
prev parent reply other threads:[~2026-11-17 10:00 UTC|newest]
Thread overview: 4+ 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 ` Paul Barker [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=DMXEDBPVHWXK.3PLBST96AJJVE@pbarker.dev \
--to=paul@pbarker.dev \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox