On Mon, May 30, 2022 at 09:08 AM, Steve Sakoman wrote:
Yes, could you fix the CVE namning issue in kirkstone with a separate
patch, and then resubmit the version bump patch based on this change?
I was checking the patch and realize that the CVE number is not wrong (I searched for the wrong CVE online),
I'm going to backport a patch for CVE-2022-1587 and then I will send the revision bump.