Fix double-free via free_rr_data nullifying local variable instead of caller's pointer

[Copilot]

free_rr_data nullified its local data copy instead of *pdata, leaving the caller's pointer dangling after the free. In loops across direct.c and forward.c, freed data[0]/data[1] pointers could be passed to reset_rr_data or freed again, triggering double-free/use-after-free.

Change

• utils.c — free_rr_data: replace data = NULL with *pdata = NULL so the caller's pointer is zeroed after the underlying struct is freed.

// Before
free(data);
data = NULL;   // only nullifies the local copy — caller's pointer still dangling

// After
free(data);
*pdata = NULL; // nullifies the caller's pointer

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud