Skip to content
VulniPulse
Advisory severityMedium4.4Red Hat Linux

Medium [CVE-2025-5278] heap buffer under-read in gnu coreutils sort via key specification

This medium-severity Red Hat Linux advisory covers CVE-2025-5278 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.

CVE-2025-5278 Source published Source updated

VulniPulse record published

Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Summary

A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read.

The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.

The severity of this issue is considered Moderate rather than Critical because successful exploitation requires the use of the traditional key specification syntax with an exceptionally large character position value, which is uncommon in typical usage.

Although the vulnerability can lead to a heap buffer overflow resulting in a read one byte before the allocated buffer, it does not enable code execution, privilege escalation, or direct compromise of data confidentiality or integrity. The impact is therefore primarily limited to potential service disruption due to application crashes.

Furthermore, default RHEL configurations such as SELinux enforcement, ASLR, and memory protections reduce the likelihood of exploitation and limit the scope of any resulting impact. These safeguards, along with typical system usage patterns that do not commonly invoke the vulnerable code path, restrict exploitability in default and hardened environments.

Is CVE-2025-5278 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2025-5278 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2025-5278?

Upgrade to a fixed release named by Red Hat:

  • coreutils-0:9.5-8.el10_2
  • coreutils-0:8.30-21.el8_10
  • coreutils-0:8.32-41.el9_8
  • cert-manager/jetstack-cert-manager-acmesolver-rhel9:1791371080
  • cert-manager/jetstack-cert-manager-rhel9:1791371069
  • cert-manager/cert-manager-operator-rhel9:1791788287
  • cert-manager/cert-manager-operator-bundle:1791970484
  • cert-manager/jetstack-cert-manager-acmesolver-rhel9:1791459707
  • cert-manager/jetstack-cert-manager-rhel9:1791459711
  • cert-manager/cert-manager-istio-csr-rhel9:1791459759
  • cert-manager/cert-manager-operator-rhel9:1789029076
  • cert-manager/cert-manager-operator-bundle:1791966259

38 more fixed releases are listed below.

Confirm against the vendor advisory before you patch.

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 17 days ago·verify at source

Fixed versions
  • coreutils-0:9.5-8.el10_2
  • coreutils-0:8.30-21.el8_10
  • coreutils-0:8.32-41.el9_8
  • cert-manager/jetstack-cert-manager-acmesolver-rhel9:1791371080
  • cert-manager/jetstack-cert-manager-rhel9:1791371069
  • cert-manager/cert-manager-operator-rhel9:1791788287
  • cert-manager/cert-manager-operator-bundle:1791970484
  • cert-manager/jetstack-cert-manager-acmesolver-rhel9:1791459707
  • cert-manager/jetstack-cert-manager-rhel9:1791459711
  • cert-manager/cert-manager-istio-csr-rhel9:1791459759
  • cert-manager/cert-manager-operator-rhel9:1789029076
  • cert-manager/cert-manager-operator-bundle:1791966259
  • cert-manager/cert-manager-trust-manager-rhel9:1790598593
  • costmanagement/costmanagement-metrics-rhel9-operator:1783539156
  • discovery/discovery-ui-rhel9:1782756541
  • discovery/discovery-server-rhel9:1784821670
  • insights-proxy/insights-proxy-container-rhel9:1782890503
  • rhosdt/tempo-gateway-opa-rhel9:1782501180
  • rhosdt/tempo-gateway-rhel9:1782501200
  • rhosdt/tempo-jaeger-query-rhel9:1782498923
  • rhosdt/tempo-operator-bundle:1782510941
  • rhosdt/tempo-query-rhel9:1782501220
  • rhosdt/tempo-rhel9:1782501196
  • rhosdt/tempo-rhel9-operator:1782501195
  • rhosdt/opentelemetry-collector-rhel9:1785704636
  • rhosdt/opentelemetry-rhel9-operator:1785704547
  • rhui5/cds-kubernetes-rhel9:1784794818
  • rhui5/cds-rhel9:1784794778
  • rhui5/haproxy-rhel9:1784795112
  • rhui5/installer-rhel9:1784794289
  • rhui5/rhua-rhel9:1784795076
  • rhui5/cds-kubernetes-tp-rhel9:1787241211
  • rhui5/installer-tp-rhel9:1787135742
  • rhui5/rhua-tp-rhel9:1787241260
  • RHSA-2026:33124
  • RHSA-2026:69964
  • RHSA-2026:28911
  • RHSA-2026:82304
  • RHSA-2026:82322
  • RHSA-2026:82888
  • RHSA-2026:82347
  • RHSA-2026:82354
  • RHSA-2026:82372
  • RHSA-2026:82857
  • RHSA-2026:72502
  • RHSA-2026:39981
  • RHSA-2026:33313
  • RHSA-2026:46836
  • RHSA-2026:34102
  • RHSA-2026:33612

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

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

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

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

See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything 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 RHEL & SELinux
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

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.