From: Lucas De Marchi <lucas.demarchi@intel.com>
To: Seung-Woo Kim <sw0312.kim@samsung.com>
Cc: linux-modules@vger.kernel.org, lucas.de.marchi@gmail.com,
gladkov.alexey@gmail.com, sungguk.na@samsung.com
Subject: Re: [PATCH 0/2] harden libkmod-builtin with wrong modules.builtin.modinfo
Date: Sat, 17 Apr 2021 13:58:44 -0700 [thread overview]
Message-ID: <20210417205844.z4ano23b7wg5drvh@ldmartin-desk2> (raw)
In-Reply-To: <20210413112315.18907-1-sw0312.kim@samsung.com>
On Tue, Apr 13, 2021 at 08:23:13PM +0900, Seung-Woo Kim wrote:
>The wrong data in modules.builtin.modinfo can cause overflow or
>double free from modinfo with libkmod-builtin. Fix the error
>cases with strict checking.
>
>Seung-Woo Kim (2):
> libkmod: fix an overflow with wrong modules.builtin.modinfo
> libkmod: fix possible double free with wrong modules.builtin.modinfo
both commits applied,
thanks
Lucas De Marchi
>
> libkmod/libkmod-builtin.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>--
>2.19.2
>
prev parent reply other threads:[~2021-04-17 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210413112018epcas1p15c2cb9693086133c145845030df145ef@epcas1p1.samsung.com>
2021-04-13 11:23 ` [PATCH 0/2] harden libkmod-builtin with wrong modules.builtin.modinfo Seung-Woo Kim
[not found] ` <CGME20210413112018epcas1p4e7e6b23060a83694867b07a1f1afc200@epcas1p4.samsung.com>
2021-04-13 11:23 ` [PATCH 1/2] libkmod: fix an overflow " Seung-Woo Kim
[not found] ` <CGME20210413112019epcas1p22c64b861d296333a64c348020c7ca20e@epcas1p2.samsung.com>
2021-04-13 11:23 ` [PATCH 2/2] libkmod: fix possible double free " Seung-Woo Kim
2021-04-17 20:58 ` Lucas De Marchi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210417205844.z4ano23b7wg5drvh@ldmartin-desk2 \
--to=lucas.demarchi@intel.com \
--cc=gladkov.alexey@gmail.com \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=sungguk.na@samsung.com \
--cc=sw0312.kim@samsung.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.