From: Takashi Iwai <tiwai@suse.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-hams@vger.kernel.org
Subject: Any fix for CVE-2022-1247?
Date: Fri, 10 Jun 2022 15:08:05 +0200 [thread overview]
Message-ID: <878rq4vf7u.wl-tiwai@suse.de> (raw)
Hi,
there is an open security issue for rose layer, CVE-2022-1247 (*), and
this doesn't seem addressed yet in the upstream.
Any chance to get this fixed?
(*) https://bugzilla.redhat.com/show_bug.cgi?id=2066799
I guess we can fix it by moving the "use" refcount increment into
rose_get_neigh(), but it cannot be verified as we haven't seen a PoC
code...
thanks,
Takashi
reply other threads:[~2022-06-10 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=878rq4vf7u.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-hams@vger.kernel.org \
--cc=ralf@linux-mips.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).