From: Stephen Hemminger <stephen@networkplumber.org>
To: samuel@sortiz.org
Cc: netdev@vger.kernel.org
Subject: Fw: [Bug 196533] New: kernel stack infoleaks
Date: Sun, 30 Jul 2017 11:03:22 -0700 [thread overview]
Message-ID: <20170730110322.2f8171ea@xeon-e3> (raw)
Begin forwarded message:
Date: Sun, 30 Jul 2017 05:13:08 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 196533] New: kernel stack infoleaks
https://bugzilla.kernel.org/show_bug.cgi?id=196533
Bug ID: 196533
Summary: kernel stack infoleaks
Product: Networking
Version: 2.5
Kernel Version: 4.12.2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: sohu0106@126.com
Regression: No
bug in net/irda/af_irda.c
Sometimes irda_getsockopt() doesn't initialize all members of list field of
irda_device_list struct. This structure is then copied to
userland. It leads to leaking of contents of kernel stack memory. We have to
initialize them to zero , or it will allows local users to obtain potentially
sensitive information from kernel stack memory by reading a copy of this
structure
https://github.com/torvalds/linux/pull/440
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2017-07-30 18:03 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=20170730110322.2f8171ea@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.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.