A flaw was found in the asynchronous message queue handling of the libsoup library, widely used by GNOME and WebKit-based applications to manage HTTP/2 communications. When network operations are aborted at specific timing intervals, an internal message queue item may be freed twice due to missing state synchronization. This leads to a use-after-free memory access, potentially crashing the affected application. Attackers could exploit this behavior remotely by triggering specific HTTP/2 read and cancel sequences, resulting in a denial-of-service condition.
Weakness
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | libsoup3-0:3.6.5-3.el10_1.7 | * |
| Red Hat Enterprise Linux 10.0 Extended Update Support | RedHat | libsoup3-0:3.6.5-3.el10_0.10 | * |
| Libsoup2.4 | Ubuntu | upstream | * |
| Libsoup3 | Ubuntu | esm-apps/jammy | * |
| Libsoup3 | Ubuntu | jammy | * |
| Libsoup3 | Ubuntu | noble | * |
| Libsoup3 | Ubuntu | plucky | * |
| Libsoup3 | Ubuntu | questing | * |
| Libsoup3 | Ubuntu | upstream | * |