We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2025-6052

Glib: integer overflow in g_string_maybe_expand() leading to potential buffer overflow in glib gstring



Description

A flaw was found in how GLib’s GString manages memory when adding data to strings. If a string is already very large, combining it with more input can cause a hidden overflow in the size calculation. This makes the system think it has enough memory when it doesn’t. As a result, data may be written past the end of the allocated memory, leading to crashes or memory corruption.

Reserved 2025-06-13 | Published 2025-06-13 | Updated 2025-06-13 | Assigner redhat


LOW: 3.7CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Problem types

Integer Overflow or Wraparound

Product status

Default status
unaffected

Default status
affected

Default status
unaffected

Default status
unaffected

Default status
affected

Default status
unaffected

Default status
unaffected

Default status
unaffected

Default status
unaffected

Default status
unaffected

Default status
unaffected

Default status
unaffected

Default status
unaffected

Default status
unaffected

Default status
affected

Timeline

2025-06-13:Reported to Red Hat.
2025-06-13:Made public.

Credits

Red Hat would like to thank Philip Withnall for reporting this issue.

References

access.redhat.com/security/cve/CVE-2025-6052 vdb-entry

bugzilla.redhat.com/show_bug.cgi?id=2372666 (RHBZ#2372666) issue-tracking

cve.org (CVE-2025-6052)

nvd.nist.gov (CVE-2025-6052)

Download JSON

Share this page
https://cve.threatint.eu/CVE/CVE-2025-6052

Support options

Helpdesk Chat, Email, Knowledgebase