CVE-2025-5278: Coreutils: heap buffer under-read in gnu coreutils sort via key specification

Published May 27, 2025
·
Updated

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.

Other sources

Coreutils: heap buffer under-read in gnu coreutils sort via key specification

Microsoft

The vulnerability occurs in pointer arithmetic when parsing an unusually large key value (UINTMAXMAX) in traditional key syntax (+POS1.C1). If a user executes a crafted command like sort +0.18446744073709551615R, pointer arithmetic may wrap around and return a pointer before the start of the allocated buffer. This flaw can lead to an out-of-bounds memory read and potentially information disclosure.

Affected Versions: GNU Coreutils versions 7.2 through the current version are affected.

Red Hat

Affected Software

3 affected componentsFixes available
GNU Coreutils>=7.2<
debian/coreutils<=8.32-4, <=9.1-1, <=9.7-3, <=9.10-1
Microsoft azl3 coreutils 9.4-7<9.4-7
9.4-7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.4-7

Event History

May 27, 2025
Data Sourced
via Red Hat·02:09 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·08:52 PM
Data Sourced
via MITRE·08:52 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
DescriptionSeverityWeakness
May 19, 2026
Data Sourced
via Debian·06:58 PM
DescriptionAffected Software
Jul 25, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-5278?

CVE-2025-5278 is classified as a high severity vulnerability due to its potential to cause application crashes and access to unauthorized memory.

2

How do I fix CVE-2025-5278?

To fix CVE-2025-5278, update GNU Coreutils to a version later than 7.2 that addresses this vulnerability.

3

What impact does CVE-2025-5278 have on my system?

CVE-2025-5278 may allow attackers to cause a crash or exploit the sort utility through crafted input.

4

Which versions of GNU Coreutils are affected by CVE-2025-5278?

GNU Coreutils versions prior to 7.2 are affected by CVE-2025-5278.

5

Can exploiting CVE-2025-5278 lead to code execution?

Exploitation of CVE-2025-5278 primarily allows for crashing the application, although it may pose risks for further exploits under specific conditions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203