CVE-2026-124743 json
Busybox: divide-by-zero and heap over-read in the volume_id hfs+ prober
published 23h ago modified 14h ago also EUVD-2026-123360
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
A flaw was found in BusyBox. When processing filesystem metadata, the volume identification component does not properly validate header values in HFS+ filesystems. An attacker able to attach a storage device or supply a specially crafted filesystem image can trigger an application crash, resulting in a Denial of Service (DoS) and preventing device resolution.
Is CVE-2026-124743 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-124743 updated cvss 5.5
busybox: Divide-by-zero and heap over-read in the volume_id HFS+ prober
-
Red Hat Enterprise Linux 6 busybox, busybox-petitbootaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Hardened Images busyboxaffected: workaround, no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected products
- Red Hat Red Hat Enterprise Linux 6
- Red Hat Red Hat Hardened Images
Classification
- Weakness
-
- CWE-369 Divide By Zero
References
-
access.redhat.com
/security/cve/CVE-2026-124743
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2571624
issue-tracking
Sources
- CVE List CVE-2026-124743
- NVD CVE-2026-124743
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.