lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aRc0DDW-HrulilN6@localhost.localdomain>
Date: Fri, 14 Nov 2025 14:52:12 +0100
From: Frederic Weisbecker <frederic@...nel.org>
To: Eslam Khafagy <eslam.medhat1993@...il.com>
Cc: anna-maria@...utronix.de, tglx@...utronix.de, gorcunov@...il.com,
	syzkaller-bugs@...glegroups.com, linux-kernel@...r.kernel.org,
	syzbot+9c47ad18f978d4394986@...kaller.appspotmail.com
Subject: Re: [PATCH v2] posix-timers: Fix potential memory leak in
 do_timer_create()

Le Fri, Nov 14, 2025 at 02:27:39PM +0200, Eslam Khafagy a écrit :
> potential memory leak may happen if user space pointer created_timer_id
> is invallid. or the value it points to is invalid. the call will
> prematurely return.
> However it doesn't free the memory it allocates with
> alloc_posix_timer(). This patch attempts to fix that by moving parameter
> check before alloc_posix_timer().
> 
> Reported-by: syzbot+9c47ad18f978d4394986@...kaller.appspotmail.com
> Closes: https://lore.kernel.org/all/69155df4.a70a0220.3124cb.0017.GAE@google.com/T/
> Fixes: ec2d0c04624b3 ("posix-timers: Provide a mechanism to allocate a given timer ID")
> Suggested-by: Cyrill Gorcunov <gorcunov@...il.com>
> Signed-off-by: Eslam Khafagy <eslam.medhat1993@...il.com>

Reviewed-by: Frederic Weisbecker <frederic@...nel.org>

-- 
Frederic Weisbecker
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ