linux-kernel - [patch 2/5] Apply the PG_sensitive flag to mac80211 WEP key handling

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>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 May 2009 11:47:13 -0700
From:	"Larry H." <research@...reption.com>
To:	linux-kernel@...r.kernel.org
Cc:	Linus Torvalds <torvalds@...l.org>, linux-mm@...ck.org,
	Ingo Molnar <mingo@...hat.com>, pageexec@...email.hu,
	linux-wireless@...r.kernel.org
Subject: [patch 2/5] Apply the PG_sensitive flag to mac80211 WEP key
	handling

This patch deploys the use of the PG_sensitive page allocator flag
within the mac80211 driver, more specifically the handling of WEP
RC4 keys during encryption and decryption.

Signed-off-by: Larry H. <research@...reption.com>

---
 net/mac80211/wep.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Index: linux-2.6/net/mac80211/wep.c
===================================================================
--- linux-2.6.orig/net/mac80211/wep.c
+++ linux-2.6/net/mac80211/wep.c
@@ -155,7 +155,7 @@ int ieee80211_wep_encrypt(struct ieee802
 		return -1;
 
 	klen = 3 + key->conf.keylen;
-	rc4key = kmalloc(klen, GFP_ATOMIC);
+	rc4key = kmalloc(klen, GFP_ATOMIC | GFP_SENSITIVE);
 	if (!rc4key)
 		return -1;
 
@@ -243,7 +243,7 @@ int ieee80211_wep_decrypt(struct ieee802
 
 	klen = 3 + key->conf.keylen;
 
-	rc4key = kmalloc(klen, GFP_ATOMIC);
+	rc4key = kmalloc(klen, GFP_ATOMIC | GFP_SENSITIVE);
 	if (!rc4key)
 		return -1;
 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/