The problematic KSP versions are between 20.0.0-8764 to 20.0.0-8777, and 20.0.1-5250 to 20.0.1-6690 for all Linux platforms.

An affected system has a call stack as shown below.

[4293952.709851] Call Trace:

[4293952.709923]  [<ffffffffc0bc9eab>] bmhook_cleanup_object+0xbb/0x360 [bmhook] <<-----

[4293952.710008]  [<ffffffffc0bcd4e7>] bmhook_free_object+0x17/0x40 [bmhook]

[4293952.710104]  [<ffffffffc0bd26ef>] bmhook_put_data+0x2f/0x50 [bmhook]

[4293952.710208]  [<ffffffffc0bd292f>] bmhook_cleanup_data+0xbf/0x180 [bmhook]

[4293952.710297]  [<ffffffffc0bd2b8a>] bmhook_posthook_handler+0x19a/0x3b0 [bmhook] <<-----

[4293952.712372]  [<ffffffffc0a466e3>] tmhook_invoke_posthooks+0x43/0xc0 [tmhook]

[4293952.713378]  [<ffffffffc0a469d6>] tmhook_nonsysentry_handler+0x1b6/0x370 [tmhook]

[4293952.714382]  [<ffffffff979c5938>] stub_execve+0x48/0x80

[4293952.715383] Code: 8b 15 20 4b 9e 00 48 01 d8 72 0e 48 c7 c2 00 00 00 80 48 2b 15 fd 27 a1 00 48 01 d0 48 c1 e8 0c 48 c1 e0 06 48 03 05 db 27 a1 00 <48> 8b 10 80 e6 80 0f 85 c8 00 00 00 49 89 c3 49 8b 03 a8 80 0f

[4293952.717547] RIP  [<ffffffff97433515>] kfree+0x55/0x140

[4293952.718572]  RSP <ffff9fa993b03ca8>

[4293952.719584] CR2: ffffec3182346880

If the call stack from vmcore analysis contains the “bmhook_cleanup_object” API call, then it is related to this issue.

To resolve this issue customers should update their KSP version to:

• 20.0.0-8778 and above (for all Linux platforms)
• 20.0.1-6749 and above (for all Linux platforms)