Bug 16068 - CTDB read-only record handling contains use after free and resource leak bugs
Summary: CTDB read-only record handling contains use after free and resource leak bugs
Status: ASSIGNED
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: CTDB (show other bugs)
Version: 4.24.2
Hardware: All All
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba release manager
QA Contact: Samba release manager
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-05-06 04:18 UTC by Martin Schwenke
Modified: 2026-05-12 15:56 UTC (History)
1 user (show)

See Also:

Attachments
Patch for v4-24-test, v4-23-test (3.39 KB, patch)
2026-05-07 07:09 UTC, Martin Schwenke 		anoopcs: review+
Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schwenke 2026-05-06 04:18:29 UTC 
All recent versions of CTDB contain a use after free and resource leak bug.  Reporting them under a single bug because both issues are contained within a couple of lines of code, so don't really need to be tracked separately.
Comment 1 Samba QA Contact 2026-05-06 05:29:03 UTC 
This bug was referenced in samba master:

88e09693a434d06ab57b14c1c1afe5996422ca0a
67f139ad28c6a771bac488b09d52dda81f3ffe81
Comment 2 Martin Schwenke 2026-05-07 07:09:01 UTC 
Created attachment 18959 [details]
Patch for v4-24-test, v4-23-test

Cherry picks cleanly into v4-24-test. Resulting patch applies cleanly to v4-23-test with git am.  Compiles in both versions.  No relevant code differences to warrant deep testing, since this is a fix to an error path.
Comment 3 Anoop C S 2026-05-07 08:29:23 UTC 
Comment on attachment 18959 [details]
Patch for v4-24-test, v4-23-test

Re-assigning for inclusion in 4.24 and 4.23.
Comment 4 Samba QA Contact 2026-05-12 14:58:26 UTC 
This bug was referenced in samba v4-24-test:

947903170c1e62d9adcb40797fb74cf2bf8f4c64
030c6f178f888ea28eca8e2e9e49e5dd56e15d44
Comment 5 Samba QA Contact 2026-05-12 15:56:03 UTC 
This bug was referenced in samba v4-24-stable (Release samba-4.24.2):

947903170c1e62d9adcb40797fb74cf2bf8f4c64
030c6f178f888ea28eca8e2e9e49e5dd56e15d44