BusyBox. An integer overflow occurs · Integer Overflow
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 11 Nov 2026, 16:32 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.5 |
|---|
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Enterprise Linux 6busybox | Affected– | Fixed in– |
| Red Hat Hardened Imagesbusybox | Affected– | Fixed in– |
AI-suggested
Mitigation options are limited. Users should avoid using BusyBox utilities for probing untrusted filesystem images in environments where this vulnerability is a concern. Standard Red Hat Enterprise Linux systems using util-linux are not affected. Monitoring vendor advisories for future updates is recommended.
Description
An integer overflow vulnerability exists in the volume_id component of BusyBox when calculating buffer boundaries during filesystem metadata probing. This flaw can be triggered by an attacker supplying a specially crafted filesystem image on an attached storage device. Exploitation causes utilities like blkid, findfs, or mount to crash, resulting in a denial of service that prevents mounting or resolving storage devices. The vulnerability primarily affects minimal environments using BusyBox for filesystem probing, such as rescue shells or specialized containers. Standard Red Hat Enterprise Linux systems are largely unaffected as they use util-linux instead of BusyBox for these operations. No fix currently meets Red Hat's criteria for deployment, and mitigation options are limited.