From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: Sasha Levin <Alexander.Levin@microsoft.com>,
stable <stable@vger.kernel.org>
Subject: Re: [4.4] Security fixes
Date: Tue, 4 Jun 2019 16:50:07 +0200 [thread overview]
Message-ID: <20190604145007.GA5824@kroah.com> (raw)
In-Reply-To: <1559226139.2631.30.camel@codethink.co.uk>
On Thu, May 30, 2019 at 03:22:19PM +0100, Ben Hutchings wrote:
> I've attached the following fixes to 4.4, as an mbox:
>
> - binder: Replace "%p" with "%pK" for stable
> - binder: replace "%p" with "%pK"
> - net: create skb_gso_validate_mac_len()
> - bnx2x: disable GSO where gso_size is too big for hardware
> - brcmfmac: Add length checks on firmware events
> - brcmfmac: screening firmware event packet
> - brcmfmac: revise handling events in receive path
> - brcmfmac: fix incorrect event channel deduction
> - brcmfmac: add length checks in scheduled scan result handler
> - brcmfmac: add subtype check for event handling in data path
> - userfaultfd: don't pin the user memory in userfaultfd_file_create()
> - coredump: fix race condition between mmget_not_zero()/get_task_mm() and core dumping
>
> The userfaultfd commit might not be a security fix but the next one
> depends on it.
All now applied, thanks.
greg k-h
next prev parent reply other threads:[~2019-06-04 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 14:22 [4.4] Security fixes Ben Hutchings
2019-06-04 14:50 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-21 22:20 Ben Hutchings
2020-05-21 23:36 ` Sasha Levin
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=20190604145007.GA5824@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alexander.Levin@microsoft.com \
--cc=ben.hutchings@codethink.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox