From 3833bd5d55552962060be49f5821e8b4ebd56862 Mon Sep 17 00:00:00 2001
From: Charalampos Stratakis <cstratak@redhat.com>
Date: Wed, 14 Jan 2026 04:50:19 +0100
Subject: [PATCH] BUG: initialize save_value field to fix uninitialized memory
 use

When a HighsSimplexBadBasisChangeRecord is created, save_value is not
set until later in applyTabooRowOut/applyTabooVariableIn. Pushing the
struct with an uninitialized field copies garbage memory.

Found via Coverity static analysis
---
 highs/simplex/SimplexStruct.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/highs/simplex/SimplexStruct.h b/highs/simplex/SimplexStruct.h
index ff37102f50..a8b8360375 100644
--- a/highs/simplex/SimplexStruct.h
+++ b/highs/simplex/SimplexStruct.h
@@ -249,7 +249,7 @@ struct HighsSimplexBadBasisChangeRecord {
   HighsInt variable_out;
   HighsInt variable_in;
   BadBasisChangeReason reason;
-  double save_value;
+  double save_value = 0.0;
 };
 
 struct HighsRayRecord {