Bug 2550505 (CVE-2026-109944)

Summary: CVE-2026-109944 freerdp: FreeRDP 3.0.0 before 3.32.0 Reachable Assertion via Stale Smartcard Handle
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in FreeRDP. When smartcard emulation and redirection are enabled, a malicious Remote Desktop Protocol (RDP) server can cause a Denial of Service (DoS) by crashing the connecting client. This issue occurs because FreeRDP fails to remove card handles when releasing a smartcard emulation context. By issuing subsequent smartcard transmit requests using the stale handle, the server triggers an internal assertion failure that abruptly terminates the client application.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2560794    
Bug Blocks:    

Description OSIDB Bzimport 2026-10-13 13:46:17 UTC
FreeRDP 3.0.0 before 3.32.0 does not remove card handles when Emulate_SCardReleaseContext releases a smartcard-emulation context, so Emulate_SCardTransmit later looks up the deleted parent context and reaches a terminating WINPR_ASSERT. A malicious RDP server can crash a connecting client with smartcard emulation and redirection enabled by releasing a context, establishing another, and issuing SCardTransmit with the stale card handle.