Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
Do not use BusyBox dpkg for package management on systems where package integrity is critical. Remove packages one at a time if BusyBox dpkg must be used. Upstream should reset field_start at the beginning of each stanza iteration in write_status_file().
Wed, 14 Oct 2026 12:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Wed, 14 Oct 2026 11:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 14 Oct 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A flaw was found in BusyBox dpkg. The write_status_file() function does not reset a field cursor between package stanzas. When two packages are removed in a single invocation and the first stanza is larger than the second, the second package stanza can be dropped from the status file, causing limited data corruption. | |
| Title | Busybox: busybox: dpkg stale field_start pointer causes out-of-bounds read and status file corruption | |
| First Time appeared |
Redhat
Redhat hummingbird |
|
| Weaknesses | CWE-125 | |
| CPEs | cpe:/a:redhat:hummingbird:1 | |
| Vendors & Products |
Redhat
Redhat hummingbird |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-10-14T10:52:14.893Z
Reserved: 2026-09-10T09:52:23.527Z
Link: CVE-2026-88842
Updated: 2026-10-14T10:52:10.160Z
Status : Received
Published: 2026-10-14T11:17:06.993
Modified: 2026-10-14T11:17:06.993
Link: CVE-2026-88842
OpenCVE Enrichment
Updated: 2026-10-14T15:15:02Z