[KUDU-3238] Use-after-free condition in Kudu C++ client upon modifying a table's partitioning

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.10.0, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.11.1, 1.13.0
• Fix Version/s: 1.14.0
• Component/s: client
• Assignee: Alexey Serbin
• Reporter: Alexey Serbin
• Created: 26/Jan/21 03:04
• Updated: 26/Jan/21 04:03
• Resolved: 26/Jan/21 03:05

Description

There was a bug in Kudu C++ client which might manifest itself upon change in a table partitioning, e.g. adding or removing a range partition and the continuing working with the same instance of Kudu client object (the latter is the recommended way of using the Kudu client in applications).

The issue might manifest itself in unexpected behavior in client applications using the Kudu C++ client library. Examples of such behavior are deadlocks, silent data corruption, and unexpected crashes with SIGBUS, SIGSEGV or even SIGABRT at some unrelated consistency check (the latter is very unlikely, though). By my knowledge, there have been no registered reports about manifestations of this bug.