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 entry this week
Date: Thu, 14 Oct 2021 08:55:45 +0200	[thread overview]
Message-ID: <20211014065545.GA18251@amd> (raw)
In-Reply-To: <CAODzB9qOyXSQ=P0x1CrPEC1=mCW3PUN4_Zx9hp0ZPpZWbM1WUw@mail.gmail.com>

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

Hi!

> * New CVEs
> 
> CVE-2021-0935: bug is in ipv6 and l2tp code.
> 
> This CVE addresses two commits, one in the ipv6 stack and the other in l2tp.
> There is two introduced commits one is 85cb73f ("net: ipv6: reset
> daddr and dport in sk if connect() fails") was merged in 4.12 and the
> other commit 3557baa ("[L2TP]: PPP over L2TP driver core") was merged
> in 2.6.23-rc1.
> 
> Fixed commits have been merged since 4.16-rc7 so 4.16 or later kernels
> don't affect this vulnerability.
> 
> Commit 2f987a76("net: ipv6: keep sk status consistent after datagram
> connect failure") fixes 85cb73f and commit b954f940("l2tp: fix races
> with ipv4-mapped ipv6 addresses") fixes commit 3557baa.
> 
> To apply patches to 4.4, it needs to fix conflicts.
> 
> CVSS v3 score is not provided.
> 
> Fixed status
> 
> mainline: [2f987a76a97773beafbc615b9c4d8fe79129a7f4,
> b954f94023dcc61388c8384f0f14eb8e42c863c5]
> stable/4.4: not fixed yet

Others are fixed, but this one may be worth watching. Fortunately it
is not remote attack, AFAICT.

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 --]

WARNING: multiple messages have this Message-ID (diff)
From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] New CVE entry this week
Date: Thu, 14 Oct 2021 08:55:45 +0200	[thread overview]
Message-ID: <20211014065545.GA18251@amd> (raw)
Message-ID: <20211014065545.8UBwMqPyAuqvT0-ttQaz_eMS75wWm-r2eAOcUTbug3s@z> (raw)
In-Reply-To: <CAODzB9qOyXSQ=P0x1CrPEC1=mCW3PUN4_Zx9hp0ZPpZWbM1WUw@mail.gmail.com>


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

Hi!

> * New CVEs
> 
> CVE-2021-0935: bug is in ipv6 and l2tp code.
> 
> This CVE addresses two commits, one in the ipv6 stack and the other in l2tp.
> There is two introduced commits one is 85cb73f ("net: ipv6: reset
> daddr and dport in sk if connect() fails") was merged in 4.12 and the
> other commit 3557baa ("[L2TP]: PPP over L2TP driver core") was merged
> in 2.6.23-rc1.
> 
> Fixed commits have been merged since 4.16-rc7 so 4.16 or later kernels
> don't affect this vulnerability.
> 
> Commit 2f987a76("net: ipv6: keep sk status consistent after datagram
> connect failure") fixes 85cb73f and commit b954f940("l2tp: fix races
> with ipv4-mapped ipv6 addresses") fixes commit 3557baa.
> 
> To apply patches to 4.4, it needs to fix conflicts.
> 
> CVSS v3 score is not provided.
> 
> Fixed status
> 
> mainline: [2f987a76a97773beafbc615b9c4d8fe79129a7f4,
> b954f94023dcc61388c8384f0f14eb8e42c863c5]
> stable/4.4: not fixed yet

Others are fixed, but this one may be worth watching. Fortunately it
is not remote attack, AFAICT.

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

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

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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6824): https://lists.cip-project.org/g/cip-dev/message/6824
Mute This Topic: https://lists.cip-project.org/mt/86301612/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/10495289/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2021-10-14  6:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 23:54 New CVE entry this week Masami Ichikawa
2021-10-13 23:54 ` [cip-dev] " Masami Ichikawa
2021-10-14  6:55 ` Pavel Machek [this message]
2021-10-14  6:55   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2021-10-21  1:21 Masami Ichikawa
2021-10-21  8:41 ` [cip-dev] " nobuhiro1.iwamatsu
2021-10-21 12:05   ` Masami Ichikawa
2021-10-07  0:59 Masami Ichikawa
2021-10-07  0:59 ` Masami Ichikawa
2021-10-07  7:30   ` Pavel Machek
2021-10-07  7:30     ` Pavel Machek
2021-10-07 11:38     ` Masami Ichikawa
2021-10-07 11:38       ` Masami Ichikawa
2021-09-30  0:12 Masami Ichikawa
2021-09-30  0:12 ` Masami Ichikawa
2021-09-30  6:33   ` nobuhiro1.iwamatsu
2021-09-30  6:33     ` Nobuhiro Iwamatsu
2021-09-30 12:11     ` Masami Ichikawa
2021-09-30 12:11       ` Masami Ichikawa
2021-09-23  1:52 Masami Ichikawa
2021-09-16  0:43 Masami Ichikawa
2021-09-16  4:55 ` Nobuhiro Iwamatsu
2021-09-09  2:39 Masami Ichikawa
2021-09-09  6:41 ` Pavel Machek
2021-09-09 12:23   ` Masami Ichikawa
     [not found] ` <CAMLqsBZCbrdOaxhuc81kvZsinS+_bFPp2tpmuVnczC1EXCA3Zg@mail.gmail.com>
2021-09-10  0:40   ` Masami Ichikawa
2021-09-02  1:05 Masami Ichikawa
2021-09-02  6:27 ` Pavel Machek
2021-09-02  7:10   ` Nobuhiro Iwamatsu
2021-09-02 12:17   ` 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=20211014065545.GA18251@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.