Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1597751 > unrolled thread

[PATCH 3.16 073/370] CIFS: Fix a possible memory corruption in push locks

Started byBen Hutchings <ben@decadent.org.uk>
First post2017-03-10 15:10 +0100
Last post2017-03-10 15:10 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  [PATCH 3.16 073/370] CIFS: Fix a possible memory corruption in  push locks Ben Hutchings <ben@decadent.org.uk> - 2017-03-10 15:10 +0100

#1597751 — [PATCH 3.16 073/370] CIFS: Fix a possible memory corruption in push locks

FromBen Hutchings <ben@decadent.org.uk>
Date2017-03-10 15:10 +0100
Subject[PATCH 3.16 073/370] CIFS: Fix a possible memory corruption in push locks
Message-ID<tjtp1-56o-57@gated-at.bofh.it>
3.16.42-rc1 review patch.  If anyone has any objections, please let me know.

------------------

From: Pavel Shilovsky <pshilov@microsoft.com>

commit e3d240e9d505fc67f8f8735836df97a794bbd946 upstream.

If maxBuf is not 0 but less than a size of SMB2 lock structure
we can end up with a memory corruption.

Signed-off-by: Pavel Shilovsky <pshilov@microsoft.com>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
---
 fs/cifs/smb2file.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/fs/cifs/smb2file.c
+++ b/fs/cifs/smb2file.c
@@ -241,7 +241,7 @@ smb2_push_mandatory_locks(struct cifsFil
 	 * and check it for zero before using.
 	 */
 	max_buf = tlink_tcon(cfile->tlink)->ses->server->maxBuf;
-	if (!max_buf) {
+	if (max_buf < sizeof(struct smb2_lock_element)) {
 		free_xid(xid);
 		return -EINVAL;
 	}

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web