Status-file corruption via stale package-field cursor
Published Oct 14, 2026 · Updated Oct 14, 2026
Status-file corruption in BusyBox dpkg allows local users to drop package records when removing two packages in one invocation. The write_status_file() function retains its field_start cursor between stanzas, causing the shorter second stanza to be omitted from the status file. The operation requires package-removal access and a larger first stanza; the matching public vendor report identifies CVE-2026-88841 rather than the supplied CVE-2026-88842.
Summary
What happened
Status-file corruption in BusyBox dpkg allows local users to drop package records when removing two packages in one invocation. The write_status_file() function retains its field_start cursor between stanzas, causing the shorter second stanza to be omitted from the status file. The operation requires package-removal access and a larger first stanza; the matching public vendor report identifies CVE-2026-88841 rather than the supplied CVE-2026-88842.
The record
- CVE
- CVE-2026-88842
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- libuser Project
- Product
- Red Hat Hardened Images
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started