Skip to content
VulniPulse
Advisory severityHigh7.5Red Hat Linux

High [CVE-2026-110752] Denial of Service via excessive memory allocation in fragment selector

This high-severity Red Hat Linux advisory covers CVE-2026-110752; related products: Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 9.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-110752 Source published Source updated

VulniPulse record published Record updated

CVE-2026-110752
Related products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Get an email when Red Hat Linux RHEL & SELinux publishes the next one.

See Red Hat Linux RHEL & SELinux's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat Linux RHEL & SELinux

Summary

Denial of Service via excessive memory allocation in fragment selector. Red Hat rates this important (CVSS 7.5).

Weakness: CWE-770.

Affected products named by the advisory: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 9; Red Hat package: perl-text-csv_xs.

Affected versions
  • < 1.65

Official advisory · high-confidence parse· fetched 12 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 · high-confidence parse· fetched 12 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to validate and restrict numeric upper bounds on row and column fragment selectors prior to invoking Text::CSV_XS fragment or csv routines: upgrade to Text::CSV_XS 1.65+ (or the fixed Perl Text Csv Xs builds), which stores range selectors as coordinate pairs and verifies index membership iteratively instead of preallocating arrays, while clamping cell column boundaries to parsed row lengths, closing all 3 injection vectors (crafted RFC 7111 row selector with large numeric range, crafted RFC 7111 col selector with large numeric range, crafted RFC 7111 cell selector with unclamped column bounds). Until patched, this is a concern on applications and services passing untrusted RFC 7111 fragment selectors to Text::CSV_XS, so strictly restrict or filter user-supplied fragment selectors to reject abnormally large range indices before passing them to fragment or csv parsing calls. As a compensating measure, restrict per-process virtual memory address space using ulimit or prlimit to contain allocation sizes, configure systemd service monitoring with WatchdogSec and automatic Restart to quickly recover from out-of-memory process terminations, and enforce cgroups v2 memory limits to isolate memory consumption and protect host-wide availability. These controls limit blast radius and contain exploitation, but they do not fix the underlying uncontrolled memory allocation defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1311 Input Size and Quantity Bounds Enforcement (high)

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

All Red Hat Linux advisories

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 34 official vendor sources and 160+ reviewed platform categories.

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.