{bp-15160} binfmt/exec: initialize binary_s to empty to avoid invaild access

[jerpelea]

Summary

binfmt/exec: initialize binary_s to empty to avoid invaild access

Included
#15124

Impact

RELEASE

Testing

CI

[nuttxpr]

[Experimental Bot, please feedback here]

No. This PR summary lacks crucial information. While it links to the PR itself, the requirements ask for a summary within the PR description, not just a title and link. The requirements ask for:

• Why is the change necessary? What problem does it solve? "Avoid invalid access" is a symptom, not a root cause. Explain what was being accessed invalidly and under what circumstances.
• What functional part of the code changed? Be more specific than binfmt/exec. Which function(s), data structures, etc., were modified?
• How does the initialization prevent the invalid access?

The impact section is also insufficient. "RELEASE" doesn't explain anything. While it might mean this is a bug fix for a release branch, it doesn't address any of the specific impact questions. Each "NO" or "YES" should be followed by a justification, even if it's a brief "N/A". For example, Impact on user: NO - This is an internal bug fix.

Finally, "CI" for testing is inadequate. The requirements explicitly ask for details about the build host and target platform(s), as well as actual test logs demonstrating the problem before the change and the correct behavior after the change. Just saying "CI" doesn't prove anything; the CI logs themselves should be referenced or included (if short).