High CPU and Memory leaks should be looked at independently. If the issue still persists, you may want to gather the relevant data and supply this to Support via a Service request:
You can see there is different data needed for different issues. Personally, I would look at why the CPU is high first.
It will be helpful to support if you can provide information such as, does it only happen on certain OS? Is the issue present straight away after a reboot or does it take some time? Does is happen all the time or does it come and go? Does the system have a specific role? etc.
this was helpful - i can confirm that applying the may update did fix the issue - we also discovered that its only affecting Virtual Machines.
Have you rebooted the servers after the update? if you have, how long it will take for the non paged memory to grow after the reboot.
I have updated over 4k servers with February release and so far I haven't seen similar issue. Makes sure you update us because it could be a new issue.
this was helpful - i can confirm that applying the may update did fix the issue - we also discovered that its only affecting Virtual Machines and Server OS version 2012R2