smtp: check transaction before to-client completion - v1 - #15869
Conversation
Make sure the transaction still exists before completing it in the to-client direction. A pipelined RSET reply may already have completed and freed it while a later end-of-DATA marker still refers to it. Found by OSS-Fuzz testcase 5498180758994944. Bug OISF#8739.
|
AI-generated review posted automatically by Suricata ai-review. Verdict: approve No actionable findings. Redmine #8739: The null guard at Linked suricata-verify PR #3231 provides adequate coverage. Its minimized 13-packet capture reproduces the pipelined Validation: reviewed the complete one-commit diff from merge base Investigator and adjudicator both used Codex CLI with model gpt-5.6-sol at xhigh reasoning effort. Codex was the final adjudicator. |
|
WARNING:
Pipeline = 32569 |
There was a problem hiding this comment.
Thanks for the work,
CI : ✅
Git ID set : looks fine for me
CLA : you already contributed :-p
Doc update : not needed
Redmine ticket : ok, make sure to include this in your backport of #15837
Tests : cool
Dependencies added: none
Code : good
Commits segmentation : simple enough
Commit messages : nice
Ticket: https://redmine.openinfosecfoundation.org/issues/8739
SV_BRANCH=OISF/suricata-verify#3231
Make sure the transaction still exists before completing it in the
to-client direction. A pipelined RSET reply may already have completed and
freed it while a later end-of-DATA marker still refers to it.
Found by OSS-Fuzz testcase 5498180758994944.