public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Pavel Machek" <pavel@ucw.cz>
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CVE-2020-10742 -- nfs client weirdness with max_rqst_size
Date: Wed, 3 Jun 2020 17:28:25 +0200	[thread overview]
Message-ID: <20200603152825.GA26103@amd> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]

Hi!

I did a bit of research on CVE-2020-10742.

Unfortunately, RedHat is a bad player here, and bug reports are partly
hidden from public.

https://bugzilla.redhat.com/show_bug.cgi?id=1824270

https://bugzilla.redhat.com/show_bug.cgi?id=1835127

The bug does not seem especially bad (it looks like it needs specific
configuration to trigger), and Salvatore Bonaccorso was not able to
trigger it in 4.19.118.

Original report is for 3.10 kernels, so that makes some sense.

I don't believe we need to do anything here.

Best regards,

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4669): https://lists.cip-project.org/g/cip-dev/message/4669
Mute This Topic: https://lists.cip-project.org/mt/74651769/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

             reply	other threads:[~2020-06-03 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 15:28 Pavel Machek [this message]
2020-06-04  9:10 ` [cip-dev] CVE-2020-10742 -- nfs client weirdness with max_rqst_size Chen-Yu Tsai

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=20200603152825.GA26103@amd \
    --to=pavel@ucw.cz \
    --cc=cip-dev@lists.cip-project.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