Medium [CVE-2026-58224] CTDB fails to do integrity checking of received packets
This medium-severity Red Hat Linux advisory covers CVE-2026-58224 affecting Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat package: ctdb.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in Samba's CTDB, the clustered database service used by Samba. Insufficient integrity validation of received CTDB protocol packets allows malformed packets containing invalid field lengths, improperly terminated strings, or inconsistent packet sizes to be processed without adequate bounds checking.
A remote attacker with access to the CTDB private network may trigger a denial of service through process crashes or excessive memory consumption and, in limited cases, disclose adjacent memory contents.
CTDB is an optional clustering component of Samba used strictly for multi-node active/active file sharing and is not installed, configured, or running by default on standard Red Hat Enterprise Linux (RHEL) deployments.
Red Hat historically supported CTDB in RHEL High Availability and Resilient Storage configurations (including RHEL 6 and RHEL 7) and officially deprecated standalone CTDB usage as of RHEL 8.4 in favor of Pacemaker-managed cluster deployments.
Network Architecture Mitigations: For legacy or historical environments actively utilizing CTDB via supported RHEL High Availability or Resilient Storage cluster configurations, Red Hat’s official Support Policies for RHEL High Availability Clusters explicitly mandate that CTDB private interconnect traffic must run on a dedicated, isolated private network segment segregated from client networks.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · medium-confidence parse· fetched 24 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · medium-confidence parse· fetched 24 days ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · medium-confidence parse· fetched 24 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.