linux-kernel - Integer overflow in target_core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAEmTpZFpyLRVY9SsTr+hT2XZcckmcu-6_pZ=NV3EEDLZ9nLFMQ@mail.gmail.com>
Date:	Fri, 22 Apr 2016 12:18:09 +0500
From:	Марк Коренберг 
	<socketpair@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Integer overflow in target_core_device.c

Linux kernel commit 8a9ebe717a133ba7bc90b06047f43cc6b8bcb8b3

attrib->max_unmap_lba_count = (q->limits.max_discard_sectors << 9)

Since max_discard_sectors is 32-bit, there may be integer overflow,
making wrong max_unmap_lba_count.

For example, LVM Thin provisioning reports that it have 16 GB maximal
discard block.

Exactly the same bug in DRBD9, I have already reported.

-- 
Segmentation fault