posix-timers: Plug potential memory leak in do_timer_create()

When posix timer creation is set to allocate a given timer ID and the
access to the user space value faults, the function terminates without
freeing the already allocated posix timer structure.

Move the allocation after the user space access to cure that.

[ tglx: Massaged change log ]

Fixes: ec2d0c04624b3 ("posix-timers: Provide a mechanism to allocate a given timer ID")
Reported-by: [e-mail]
Suggested-by: Cyrill Gorcunov <[e-mail]>
Signed-off-by: Eslam Khafagy <[e-mail]>
Signed-off-by: Thomas Gleixner <[e-mail]>
Reviewed-by: Frederic Weisbecker <[e-mail]>
Link: https://patch.msgid.link/[e-mail]
Closes: https://lore.kernel.org/all/[e-mail]/T/

kernel/time/posix-timers.c

···
 	if (!kc->timer_create)
 		return -EOPNOTSUPP;
 
-	new_timer = alloc_posix_timer();
-	if (unlikely(!new_timer))
-		return -EAGAIN;
-
-	spin_lock_init(&new_timer->it_lock);
-
 	/* Special case for CRIU to restore timers with a given timer ID. */
 	if (unlikely(current->signal->timer_create_restore_ids)) {
 		if (copy_from_user(&req_id, created_timer_id, sizeof(req_id)))
···
 		if ((unsigned int)req_id > INT_MAX)
 			return -EINVAL;
 	}
+
+	new_timer = alloc_posix_timer();
+	if (unlikely(!new_timer))
+		return -EAGAIN;
+
+	spin_lock_init(&new_timer->it_lock);
 
 	/*
 	 * Add the timer to the hash table. The timer is not yet valid