Send the whole `g_checkResult` to the UI task (#2323)
What changed, and why it matters
A firmware fix for a data-passing bug between internal tasks. The code was accidentally sending only the memory address size of a result structure, not the full result. Right now this only affects the rarely-used error_message field, but it could cause crashes or expose wrong data if future code starts reading that field. The commit message says it caused a crash during debugging.
Treat as a low-to-moderate reliability bug. If possible, obtain the actual diff to confirm the fix is complete and that all callers sending g_checkResult use the correct size. No immediate security response appears necessary unless error_message is later used for security-sensitive output.
Security signals we found
Incorrect size passed in inter-task message (sizeof pointer instead of sizeof structure)
Structure member truncation could leak partial or stale data to UI task
Crash observed by developer when accessing the omitted error_message field
Evidence from the diff
The commit changes an inter-task message so that the entire g_checkResult structure is copied to the UI task instead of only sizeof(pointer) bytes. Previously only the error_code (likely the first pointer-sized bytes) was transmitted; the error_message member was not. The patch dereferences the pointer to send the full structure. Stats show 0 changed files and no diff is available, so the exact scope cannot be verified from the supplied materials.
Changed components
Keystone 3 firmware inter-task messagingUI task result handlingg_checkResult structureInspect captured patch +0 / −0
Diff not available from the source API.Why this scored 28/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.