Hi Paul,
Thanks for the feedback. I checked the downstream package sources.
All three June patches are carried by:
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
[2] [ubuntu/stonking-proposed] busybox 1:1.38.0-3ubuntu1 (Accepted)
[3] 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/
[5] https://lists.busybox.net/pipermail/busybox/2026-July/092395.html
Regards,
Darsh
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>Hi Darsh,
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>
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