linux-kernel - Re: [PATCH] tty: fix memory leak in gsm_activate

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]

Date:   Tue, 19 Sep 2023 17:22:26 +0800
From:   Edward AD <twuufnxlz@...il.com>
To:     gregkh@...uxfoundation.org
Cc:     eadavis@...a.com, jirislaby@...nel.org,
        linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
        syzbot+b5d1f455d385b2c7da3c@...kaller.appspotmail.com,
        syzkaller-bugs@...glegroups.com, twuufnxlz@...il.com
Subject: Re: [PATCH] tty: fix memory leak in gsm_activate_mux

On Tue, 19 Sep 2023 10:29:08 +0200 Greg KH wrote:
> > When the call to gsm_register_devices() fails, we need to reclaim the memory
> > requested in gsm_dlci_alloc().
> >
> > Fixes: 01aecd917114 ("tty: n_gsm: fix tty registration before control channel open")
> > Reported-and-tested-by: syzbot+b5d1f455d385b2c7da3c@...kaller.appspotmail.com
> > Signed-off-by: Edward AD <twuufnxlz@...il.com>
> 
> Please use your company name/email address, and then just set a manual
> "From:" line as the first line in the changelog as the documentation
> asks.  That's how developers work around their broken corporate email
> systems (but really, you should go and poke your IT group to fix it.)
This repair was completed in my personal time. Additionally, there may be a 
possibility of the company's email being thrown away by 'lore.kernel.org'. 
If you are not very strict with this, I will continue to use my private email.

I will only keep one line starting with 'From:' in the patch.

Thanks,
edward