Issue Number: 700719a
| Issue | 1. Memory corruption occurs when repeatedly adding and removing Standby instances while the Primary instance is under load. 2. The activation status of the Primary instanceโs main listener does not match the state of the proxy. 3. When the runtime Standby lock is released twice, an SLOG message indicating that the lock owner count has been invalidated is output. 4. Resources are released redundantly at certain points when disabling the Standby instance or stopping the Primary instance. |
| Cause | 1. During connection handling, when a large number of messages remain in a waiting state, disconnection events may be processed before connection addition events. This leads to attempts to reconnect after resources have been released, causing access to already freed resources and corruption of the list structure, resulting in errors. 2. When changing Standby status, only the main processโs status is checked, failing to reflect the proxy status that is in intermediate processing, which can cause missing status changes. 3. At certain processing stages, locks are released but the lock information is not updated to NULL, causing duplicate releases. 4. After sending a connection release request message, connection information is not immediately updated to NULL. If a signal occurs during concurrent processing, resources are released redundantly. |
| Solutions | 1. When a waiting state occurs during message processing, events are registered directly so that resources are cleaned up when related events are released, preventing access to already freed resources. 2. When activating or deactivating Standby, both the primary network interface and the secondary network interface statuses are checked, and processing occurs only when both interfaces have the same status. 3. Locks are released before exception handling and the lock information is updated to NULL to prevent duplicate releases. 4. After sending a connection release request, connection information is immediately updated to NULL to prevent duplicate releases during concurrent processing. |
| Occurrence Date | 03/26/2026 |
| Required Patch Version | - |
Patch Information
| Patch Name | FS02PS_700719a |
| Major Version | 7 |
| Minor Version | FS02PS |
| Release Date | 05/06/2026 |
| Version Title | Fix for UAF Issue Related to conn_info in Standby |
| Default Included Version | - |
| Compatibility Information | No incompatible items โข TAC Rolling Patch: Available โข TSC Rolling Patch: Available โข Backup Data Compatibility: Available โข Protocol Compatibility: Available โข Data Format Compatibility: Available |
| AP Impact | โข Plan change: No โข Result value change: No โข SQL syntax change: No โข System object change: No โข Existing functionality change: No |
| Parameters | - |
| Workaround | - |