From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: paul@paul-moore.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] audit: always check the netlink payload length in" failed to apply to 4.19-stable tree
Date: Tue, 3 Mar 2020 13:21:57 -0500 [thread overview]
Message-ID: <20200303182157.GL21491@sasha-vm> (raw)
In-Reply-To: <15831732722521@kroah.com>
On Mon, Mar 02, 2020 at 07:21:12PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 756125289285f6e55a03861bf4b6257aa3d19a93 Mon Sep 17 00:00:00 2001
>From: Paul Moore <paul@paul-moore.com>
>Date: Mon, 24 Feb 2020 16:38:57 -0500
>Subject: [PATCH] audit: always check the netlink payload length in
> audit_receive_msg()
>
>This patch ensures that we always check the netlink payload length
>in audit_receive_msg() before we take any action on the payload
>itself.
>
>Cc: stable@vger.kernel.org
>Reported-by: syzbot+399c44bf1f43b8747403@syzkaller.appspotmail.com
>Reported-by: syzbot+e4b12d8d202701f08b6d@syzkaller.appspotmail.com
>Signed-off-by: Paul Moore <paul@paul-moore.com>
Worked around missing 626abcd13d4e ("audit: add syscall information to
CONFIG_CHANGE records") in older kernels, queued for 4.19-4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-03-03 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 18:21 FAILED: patch "[PATCH] audit: always check the netlink payload length in" failed to apply to 4.19-stable tree gregkh
2020-03-03 18:21 ` Sasha Levin [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=20200303182157.GL21491@sasha-vm \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=paul@paul-moore.com \
--cc=stable@vger.kernel.org \
/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.