CVE-2025-12105
BaseFortify
Publication date: 2025-10-23
Last updated on: 2026-03-19
Assigner: Red Hat, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gnome | libsoup | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free flaw in the libsoup library's asynchronous message queue handling for HTTP/2 communications. Specifically, when network operations are aborted at certain timing intervals, a message queue item may be freed twice due to missing state synchronization. This causes the application to access memory that has already been freed, leading to crashes or undefined behavior. Attackers can remotely trigger this by sending crafted HTTP/2 request sequences or abruptly terminating connections. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can cause denial-of-service conditions by crashing applications that use the libsoup library for HTTP/2 communications. Since it can be triggered remotely without authentication or user interaction, attackers can disrupt services relying on vulnerable versions of libsoup, potentially causing application downtime or instability. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for application crashes or denial-of-service symptoms in applications using the libsoup library, especially those handling HTTP/2 communications. Since the flaw is triggered by specific HTTP/2 read and cancel sequences causing use-after-free errors, network detection could involve capturing and analyzing HTTP/2 traffic for abnormal or crafted request sequences that abruptly terminate connections. However, no specific detection commands or tools are provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the libsoup library to a patched version that addresses the use-after-free flaw in the asynchronous message queue handling. Additionally, monitoring and restricting potentially malicious HTTP/2 traffic that could trigger the vulnerability may help reduce risk. Since exploitation can be done remotely without authentication, applying security updates promptly is critical. [1]