High [CVE-2026-16529] Denial of Service due to signed integer overflow
This high-severity Red Hat Linux advisory covers CVE-2026-16529 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
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 signed integer overflow in the PCP __pmGetPDU() function can be exploited via crafted network packets during PDU processing or SASL negotiation. This permanently blinds the affected daemon, resulting in a total denial of service (DoS) for subsequent packet reads.
This is an Important denial of service vulnerability in PCP due to a signed integer overflow. An unauthenticated remote attacker could exhaust resources by sending a specially crafted request to the pmlogger or pmcd services, leading to a permanent denial of service for the affected daemon.
While both services are typically bound to the loopback interface by default, remote exploitation is possible if the default binding configuration is altered or if PMLOGGER_LOCAL is unset for pmlogger. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
Weakness: CWE-190. Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7.
Red Hat lists Red Hat OpenShift Container Platform 4 as not affected. Will not fix / out of support: Red Hat Enterprise Linux 6.
Red Hat fixing advisory: RHSA-2026:55617, RHSA-2026:55560, RHSA-2026:55740.
Affected products named by the advisory: Red Hat package: pcp.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
- pcp-0:7.0.3-5.el10_2
- pcp-0:5.3.7-22.el8_10.5
- pcp-0:6.3.7-8.el9_8.4
- RHSA-2026:55617
- RHSA-2026:55560
- RHSA-2026:55740
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
Mitigation checklist
- To mitigate this issue, ensure that Performance Co-Pilot (PCP) services, specifically `pmlogger` and `pmcd`, are not exposed to untrusted networks. By default, these services are configured to listen only on the loopback interface, which prevents remote exploitation. If these default network bindings have been altered, revert them to restrict access to localhost. For `pmlogger`, ensure the `PMLOGGER_LOCAL` environment variable is set. If remote access to PCP services is not required, consider implementing firewall rules to block external connections to TCP ports 4330 (pmlogger) and 44321 (pmcd). Changes to network configurations or environment variables may require restarting the affected PCP services for the mitigation to take effect.
Official advisory · high-confidence parse· fetched 11 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.