linux-kernel - 3.5 kernel NULL pointer dereference net_tx

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

Message-ID: <50235D10.6080009@web.de>
Date:	Thu, 09 Aug 2012 08:47:44 +0200
From:	Jörg-Volker Peetz <jvpeetz@....de>
To:	linux-kernel@...r.kernel.org
Subject: 3.5 kernel NULL pointer dereference net_tx_action

Dear maintainers,

with kernel 3.5 on debian x86_64 and wpa_supplicant 1.0 on an MSI laptop trying
to start the wireless network adapter, results in a kernel oops:

BUG: unable to handle kernel NULL pointer dereference at 0000000000000082
IP: [<ffffffff81325e70>] net_tx_action+0xd0/0xd0
PGD 392aa067 PUD 390b7067 PMD 0
Oops: 0002 [#1]
CPU 0
Modules linked in: snd_atiixp_modem snd_atiixp snd_ac97_codec snd_pcm
snd_page_alloc ac97_bus arc4 rt2500pci eeprom_93cx6 snd_seq rt2x00pci
snd_seq_device snd_timer snd rt2x00lib mac80211 8250_pci soundcore 8139too
cfg80211 8250 pcmcia mii serial_core sdhci_pci psmouse sdhci k8temp

Pid: 2617, comm: wpa_supplicant Not tainted 3.5.0 #1 MICRO-STAR INT'L CO.,LTD
MS-1013
RIP: 0010:[<ffffffff81325e70>]  [<ffffffff81325e70>] net_tx_action+0xd0/0xd0
RSP: 0018:ffff88003862fc20  EFLAGS: 00010086
RAX: ffff880039326ef8 RBX: ffff88003932b6c0 RCX: 0000000000000000
RDX: 00000000ffffffff RSI: 0000000000000001 RDI: 0000000000000002
RBP: 00000000000000b8 R08: ffffffff813aeee0 R09: ffff88003911aa00
R10: 0000000000000001 R11: 0000000000000000 R12: ffff88003932b6c1
R13: 0000000000000000 R14: ffff8800384251d0 R15: ffff8800384244e0
FS:  00007f6acab12700(0000) GS:ffffffff8153d000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000082 CR3: 000000003972f000 CR4: 00000000000007f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process wpa_supplicant (pid: 2617, threadinfo ffff88003862e000, task
ffff88003911aa00)
Stack:
ffffffffa010189d ffff88003a12c578 ffff88003932b6c0 0000000000000001
0000000000000246 ffff8800397f2a78 0000000000000000 0000000000000001
0000000000000000 ffff8800384244e0 ffffffffa0101939 ffff8800397f2a58
Call Trace:
[<ffffffffa010189d>] ? ieee80211_propagate_queue_wake+0xfd/0x110 [mac80211]
[<ffffffffa0101939>] ? ieee80211_wake_queue_by_reason+0x9/0x10 [mac80211]
[<ffffffffa0128c2d>] ? rt2x00queue_flush_queue+0x6d/0xd0 [rt2x00lib]
[<ffffffffa01277e0>] ? rt2x00mac_flush+0x20/0x50 [rt2x00lib]
[<ffffffffa00f1fe2>] ? __ieee80211_recalc_idle+0x202/0x220 [mac80211]
[<ffffffffa00f280c>] ? ieee80211_do_open+0x19c/0x7f0 [mac80211]
[<ffffffff8132aa6e>] ? __dev_open+0x8e/0xe0
[<ffffffff8132acfa>] ? __dev_change_flags+0x9a/0x180
[<ffffffff8132ae90>] ? dev_change_flags+0x20/0x70
[<ffffffff81374857>] ? devinet_ioctl+0x667/0x7e0
[<ffffffff8131722d>] ? sock_ioctl+0x5d/0x260
[<ffffffff810a47df>] ? do_vfs_ioctl+0x8f/0x550
[<ffffffff810a8496>] ? d_kill+0xb6/0x110
[<ffffffff810a8995>] ? dput+0x65/0x130
[<ffffffff810a4ce9>] ? sys_ioctl+0x49/0x90
[<ffffffff813a87e0>] ? system_call_fastpath+0x16/0x1b
Code: db 48 89 df 75 d5 48 83 c4 08 5b 5d c3 be 96 0b 00 00 48 c7 c7 6c bd 4a 81
e8 9d e3 cf ff e9 75 ff ff ff 0f 1f 84 00 00 00 00 00 <0f> ba af 80 00 00 00 00
19 c0 85 c0 74 02 f3 c3 53 9c 5b fa 48
RIP  [<ffffffff81325e70>] net_tx_action+0xd0/0xd0
RSP <ffff88003862fc20>
CR2: 0000000000000082
---[ end trace 3590f1d9f55c8367 ]---

Sometimes the machine freezes.

I couldn't find any hints on the web.
Any clues?
Further informations about the system can be provided on request.

-- 
Best regards,
Jörg-Volker.





--
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/