fix(mdns): Fix potential mem issue with scheduled packets #920
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #917
Fixes memory leaks and use-after-free in mDNS question handling by ensuring dynamically allocated strings are freed when questions are discarded early.
Changes:
Stop freeing domain: q->domain points to MDNS_DEFAULT_DOMAIN, so it is not freed.
Switch to dynamic allocations in (Allocate host, service, and proto with mdns_mem_strndup() and set own_dynamic_memory = true)
Add cleanup in early discard paths:
Prevents leaks when questions are discarded before being queued (duplicates, NULL values, or early removal). Ensures consistency with the own_dynamic_memory flag and avoids accessing freed memory.
This aligns with the pattern used in
_mdns_free_tx_packet()for cleaning up dynamically allocated question fields.