Bug 2543279 - CVE-2026-102558 libsoup3: libsoup: Heap buffer overflow during WebSocket receive-buffer growth [fedora-all]
Summary: CVE-2026-102558 libsoup3: libsoup: Heap buffer overflow during WebSocket rece...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libsoup3
Version: 44
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Adrian Vovk
QA Contact:
URL:
Whiteboard: {"flaws": ["b941a0b0-e1e1-45da-a415-8...
Depends On:
Blocks: CVE-2026-102558
TreeView+ depends on / blocked
 
Reported: 2026-09-29 16:23 UTC by Srikanth Balasubramanian
Modified: 2026-11-12 03:14 UTC (History)
4 users (show)

Fixed In Version: libsoup3-3.6.6-11.fc44 libsoup3-3.6.6-6.fc43
Clone Of:
Environment:
Last Closed: 2026-11-03 01:38:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME/libsoup/-/work_items/554 0 None None None 2026-10-27 00:57:23 UTC

Description Srikanth Balasubramanian 2026-09-29 16:23:41 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

A heap buffer overflow was found in libsoup's WebSocket incoming receive buffer handling.

Incoming frames are accumulated in a GByteArray. With max-incoming-payload-size set to 0 (unlimited), a peer could declare a multi-GiB payload and stream it until the buffer length wrapped in g_byte_array_set_size() while the read still targeted the original offset, writing past the allocation.

Fixed by rejecting payload lengths above what the receive buffer can represent as soon as the frame header is parsed, before buffering the payload (commit 381a474f, libsoup 3.7.3). Such frames are closed as SOUP_WEBSOCKET_CLOSE_TOO_BIG.

References:
https://gitlab.gnome.org/GNOME/libsoup/-/work_items/554 (Bug 6)
https://gitlab.gnome.org/GNOME/libsoup/-/commit/381a474f

Comment 1 Adrian Vovk 2026-10-27 00:57:24 UTC
rawhide and f45 will be fixed by upgrading to 3.8 w/ mclazy

f44 and f43 will need a backport of the commit

Comment 2 Fedora Update System 2026-10-27 05:13:08 UTC
FEDORA-2026-6c3a4775a6 (libsoup3-3.6.6-6.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-6c3a4775a6

Comment 3 Fedora Update System 2026-10-27 05:13:40 UTC
FEDORA-2026-f06a7887af (libsoup3-3.6.6-11.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-f06a7887af

Comment 4 Fedora Update System 2026-10-28 03:18:11 UTC
FEDORA-2026-6c3a4775a6 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-6c3a4775a6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6c3a4775a6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2026-10-28 04:01:18 UTC
FEDORA-2026-f06a7887af has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f06a7887af`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f06a7887af

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-11-03 01:38:19 UTC
FEDORA-2026-f06a7887af (libsoup3-3.6.6-11.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2026-11-12 03:14:57 UTC
FEDORA-2026-6c3a4775a6 (libsoup3-3.6.6-6.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.