All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Sebastian Reichel <sre@kernel.org>,
	anish kumar <anish198519851985@gmail.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Anton Vorontsov <cbouatmailru@gmail.com>,
	Jonathan Cameron <jic23@kernel.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	letux-kernel@openphoenux.org, kernel@pyra-handheld.com,
	"H. Nikolaus Schaller" <hns@goldelico.com>
Subject: [PATCH 0/2] power: generic-adc-battery: fix out of bounds write
Date: Tue, 26 Jun 2018 15:28:28 +0200	[thread overview]
Message-ID: <cover.1530019688.git.hns@goldelico.com> (raw)

This patch set addresses two bugs in the gab_probe() function which are
there since the first commit in 3.7-rc1:

1. there is an out of bounds write access by a miscalculated destination
   address for the memcpy()
2. if iio channels are already represented by default properties, they
   appear as duplicates in uevent


H. Nikolaus Schaller (2):
  power: generic-adc-battery: fix out-of-bounds write when copying
    channel properties
  power: generic-adc-battery: check for duplicate properties copied from
    iio channels

 drivers/power/supply/generic-adc-battery.c | 25 +++++++++++++++----------
 1 file changed, 15 insertions(+), 10 deletions(-)

-- 
2.12.2

             reply	other threads:[~2018-06-26 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 13:28 H. Nikolaus Schaller [this message]
2018-06-26 13:28 ` [PATCH 1/2] power: generic-adc-battery: fix out-of-bounds write when copying channel properties H. Nikolaus Schaller
2018-06-26 13:28 ` [PATCH 2/2] power: generic-adc-battery: check for duplicate properties copied from iio channels H. Nikolaus Schaller
2018-07-06 17:00 ` [PATCH 0/2] power: generic-adc-battery: fix out of bounds write Sebastian Reichel

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=cover.1530019688.git.hns@goldelico.com \
    --to=hns@goldelico.com \
    --cc=anish198519851985@gmail.com \
    --cc=cbouatmailru@gmail.com \
    --cc=jic23@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=kernel@pyra-handheld.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@kernel.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.