Memory will be allocated by multiple processes. The corresponding free function must be used to free the memory. It would otherwise cause memory corruption or memory leak.
In this memory corruption issue, there is a mismatched between alloc and free functions that are used on the notification buffer.
If memory allocated by one alloc process is freed by another free process, future allocating the same memory will result in a wrong start of memory.
Eventually this will lead is a kernel space memory overrun.
This issue is fixed under CR#xos0063870 - Kernel oops occurs due to memory overrun in user kernel interface.