All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] New CVE entries in this week
Date: Thu, 13 Jan 2022 09:07:43 +0100	[thread overview]
Message-ID: <20220113080742.GA15000@amd> (raw)
In-Reply-To: <CAODzB9ojKHaZ13TykpwVx3ot7Y45qQaZt7S0gCfag2E9Ad-Apw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]

Hi!

> * New CVEs
> 
> CVE-2021-39633: ip_gre: add validation for csum_start
> 
> CVSS v3 score is not provided
> 
> An information leak bug was found in gre_handle_offloads() which is in
> net/ipv4/ip_gre.c.
> This fix uses skb_checksum_start() to check data but this function was
> introduced at 4.6-rc1 commit 08b64fc ("net: Store checksum result for
> offloaded GSO checksums") so applying this patch requires commit
> 08b64fc too.
> 
> Fixed status
> 
> mainline: [1d011c4803c72f3907eccfc1ec63caefb852fcbf]
> stable/4.9: [41d5dfa408130433cc5f037ad89bed854bf936f7]

So this needs more investigation and possibly 4.4 port? 08b64fc looks
quite small/simple.

> CVE-2021-39634: epoll: do not insert into poll queues until all sanity
> checks are done
> 
> CVSS v3 score is not provided
> 
> A local attacker could gain his privilege by abusing this bug. All
> stable kernels and the mainline kernels have already been fixed.
> 
> Fixed status

...and 4.19 and older is fixed, and 5.10 already contains
f8d4f44df056c5b504b0d49683fb7279218fd207, so nothing to do here. Good.

> CVE-2021-4204: eBPF Improper Input Validation Vulnerability
> 
> CVSS v3 score is not provided
> 
> A local attacker can escalate privileges via this bug.
> This bug is affecting the 5.8 or later kernel. The commit 457f4436
> ("bpf: Implement BPF ring buffer and verifier support for it")
> introduced this issue.
> 
> To mitigate this issue, set kernel.unprivileged_bpf_disabled to 1.
> 
> Fixed status
> 
> Not fixed yet.

Apparently Ubuntu has a fix for this. But I guess we can wait till it
hits mainline.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

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

  reply	other threads:[~2022-01-13  8:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 23:39 New CVE entries in this week Masami Ichikawa
2022-01-13  8:07 ` Pavel Machek [this message]
2022-01-13 12:41   ` [cip-dev] " Masami Ichikawa
  -- strict thread matches above, loose matches on Subject: below --
2022-01-26 23:51 Masami Ichikawa
2022-01-27  8:21 ` [cip-dev] " nobuhiro1.iwamatsu
2022-01-28  6:18   ` Masami Ichikawa
2022-01-29 21:03 ` Pavel Machek
2022-01-31  0:00   ` Masami Ichikawa
2021-12-29 23:29 Masami Ichikawa
2021-12-30 10:20 ` [cip-dev] " Pavel Machek
2021-12-30 23:05   ` Masami Ichikawa
2021-12-23  0:48 Masami Ichikawa
2021-12-23 17:11 ` [cip-dev] " Pavel Machek
2021-12-15 23:49 Masami Ichikawa
2021-12-16  5:26 ` [cip-dev] " nobuhiro1.iwamatsu
2021-12-16  5:58   ` Masami Ichikawa
2021-12-16  8:49 ` Pavel Machek
2021-12-08 23:44 Masami Ichikawa
2021-12-09  9:20 ` [cip-dev] " Pavel Machek
2021-12-09 14:12   ` Masami Ichikawa
     [not found] <16BAA9D56D09F20A.23256@lists.cip-project.org>
2021-11-25  5:16 ` Masami Ichikawa
2021-11-25  8:00   ` nobuhiro1.iwamatsu
2021-11-25 12:00     ` Masami Ichikawa
2021-11-25  9:09   ` Pavel Machek
2021-11-25 12:01     ` Masami Ichikawa
2021-11-25  2:41 Masami Ichikawa
2021-11-25  9:14 ` [cip-dev] " Pavel Machek
2021-11-10 23:52 Masami Ichikawa
2021-11-11  9:21 ` [cip-dev] " Pavel Machek
2021-11-11 12:47   ` Masami Ichikawa
2021-11-04  1:11 New CVE Entries " Masami Ichikawa
2021-11-04  9:57 ` [cip-dev] " Pavel Machek
2021-11-04 13:04   ` Masami Ichikawa

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=20220113080742.GA15000@amd \
    --to=pavel@denx.de \
    --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 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.