All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Raphael S. Carvalho" <raphaelsc@cloudius-systems.com>
To: util-linux@vger.kernel.org
Cc: "Raphael S. Carvalho" <raphaelsc@cloudius-systems.com>
Subject: [PATCH] blkdiscard: fix underflow when offset is greater than device size
Date: Wed,  8 Oct 2014 21:46:07 -0300	[thread overview]
Message-ID: <1412815567-2565-1-git-send-email-raphael.scarv@gmail.com> (raw)

From: "Raphael S. Carvalho" <raphaelsc@cloudius-systems.com>

If offset (range[0]) is greater than device size (blksize), the variable 'end'
will be greater than blksize, and range[1] (length) will be recalculated.
The underflow happens when subtracting range[0] (offset) from blksize, thus
range[1] will be the result of an underflow. The bug leads to unwanted behavior
from the program, where range[1] is likely to be a high number and then will
discard a considerable amount of blocks from the device. The fix consists of
exitting the program with an error message when the condition stated above is
true. Spotted while auditing the code.

Signed-off-by: Raphael S. Carvalho <raphaelsc@cloudius-systems.com>
---
 sys-utils/blkdiscard.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sys-utils/blkdiscard.c b/sys-utils/blkdiscard.c
index 2ddcdb1..2f22af7 100644
--- a/sys-utils/blkdiscard.c
+++ b/sys-utils/blkdiscard.c
@@ -149,6 +149,8 @@ int main(int argc, char **argv)
 	range[1] &= ~(secsize - 1);
 
 	/* is the range end behind the end of the device ?*/
+	if (range[0] > blksize)
+		err(EXIT_FAILURE, _("%s: offset is greater than device size"), path);
 	end = range[0] + range[1];
 	if (end < range[0] || end > blksize)
 		range[1] = blksize - range[0];
-- 
1.9.3


             reply	other threads:[~2014-10-09  0:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09  0:46 Raphael S. Carvalho [this message]
2014-10-14 10:14 ` [PATCH] blkdiscard: fix underflow when offset is greater than device size Karel Zak

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=1412815567-2565-1-git-send-email-raphael.scarv@gmail.com \
    --to=raphaelsc@cloudius-systems.com \
    --cc=util-linux@vger.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.