BUSYBOX · CVE-2026-124742 · Runtime
NO FIX YET
A malformed FAT filesystem can make BusyBox's volume identification code divide by zero and crash. An attacker who can present a crafted storage device or disk image can cause a denial of service that disrupts device discovery and boot.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems that run BusyBox utilities such as blkid or mdev and automatically probe attached storage or disk images, typically embedded devices and minimal Linux images. Systems that never scan untrusted disks or images are unlikely to be reached. The sources do not list affected versions.
Not affected if no-untrusted-disks
Who cares busybox, embedded-linux, linux
busybox --help on systems that ship itNo fix yet, per the sources.
A flaw was found in BusyBox. The volume identification component fails to properly validate cluster parameters when analyzing specially formatted FAT filesystems. An attacker able to present a crafted storage device or disk image can trigger a divide-by-zero condition when partition scanning utilities inspect the volume. This issue causes the probing utilities to crash unexpectedly, resulting in a Denial of Service (DoS) that can disrupt device discovery and system boot operations.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.