CVE-2026-124742

Busybox: divide-by-zero in the volume_id fat prober via a zero sectors_per_cluster value

  • Medium 5.5

Description

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.

Key facts

Published
11 Nov 2026
Last changed
13 Nov 2026
Assigned by
redhat
EPSS
0.189% likely to be exploited in the next 30 days, higher than 8.569% of CVEs (scores for 15 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.5CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

What to do

  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Hardened Images
  • Default status: affected
  • 1.37.0-9.5.hum1 up to but excluding * (unaffected)
Red HatRed Hat Enterprise Linux 6
  • Default status: unknown

Timeline

  1. 25 Oct 2026 Reported to Red Hat.
  2. 11 Nov 2026 Made public.
  3. 11 Nov 2026 Published

Weakness

References