CWE-369
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 11 Nov 2026, 13:27 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
According to the Red Hat advisory, no effective mitigation or patch is currently available that meets their criteria for ease of use, applicability, or stability. Exposure is limited in standard Red Hat Enterprise Linux environments because BusyBox is not used for core storage probing. Users should be aware of the risk primarily in recovery or minimal container environments where BusyBox is used. Monitoring for future patches or updates from vendors is recommended.
Description
A vulnerability in BusyBox's volume identification component causes improper validation of cluster parameters in specially crafted FAT filesystems. This flaw can trigger a divide-by-zero error during partition scanning, leading to a crash of probing utilities. The resulting denial of service can disrupt device discovery and system boot processes. The issue requires local access or the ability to present crafted storage media. In typical Red Hat Enterprise Linux environments, exposure is limited as BusyBox is not the default for storage probing. No effective mitigation or patch is currently available.