The primary vulnerable function, JOIN::fix_all_splittings_in_plan, is identified directly from the CVE description and the Jira issue MDEV-32084, which includes a stack trace pinpointing the crash. The other functions, JOIN::optimize_inner and JOIN::optimize, are identified from the same stack trace as they are part of the call chain leading to the vulnerable function. Confidence is high for JOIN::fix_all_splittings_in_plan due to direct mentions and stack trace evidence. Confidence is medium for the other functions as they are part of the vulnerable execution path but not the direct source of the crash. No commit information was available to analyze the patch directly, so the analysis relies on the provided descriptions and stack trace.