linux-kernel - Re: BUG kmalloc-2048: Poison overwritten

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: <20080601190138.4d86dc66@infradead.org>
Date:	Sun, 1 Jun 2008 19:01:38 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Justin Mattock" <justinmattock@...il.com>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: BUG kmalloc-2048: Poison overwritten

On Sun, 1 Jun 2008 23:13:51 +0000
"Justin Mattock" <justinmattock@...il.com> wrote:

> I received this after the second simultaneous suspend: (I will try and
> see if this is re creatable or not)
> 
> [  232.270737] BUG: unable to handle kernel paging request at 6b6b6c6b

bad bad bad


> [  232.270743] IP: [<c013f96d>] module_put+0x12/0x2b
> [  232.270750] *pde = 00000000
> [  232.270753] Oops: 0002 [#1] SMP
> [  232.270757] Modules linked in: hci_usb cpufreq_ondemand
> cpufreq_performance cpufreq_powersave rfcomm hidp l2cap bluetooth fan
> ipmi_watchdog ipmi_msghandler uinput wlan_tkip ieee80211_crypt_tkip
> ieee80211_crypt arpt_mangle arptable_filter arp_tables
> nf_conntrack_ipv4 nf_conntrack iptable_mangle iptable_filter ip_tables
> x_tables intelfb i2c_i810 i2c_algo_bit coretemp eeprom acpi_cpufreq
> fglrx(P) applesmc joydev uvcvideo appletouch wlan_scan_sta
   ^^^^^

naughty

> ath_rate_sample firewire_ohci firewire_core snd_hda_intel ath_pci
> snd_pcm wlan ohci1394 intel_agp evdev ath_hal(P) snd_timer ieee1394
                                        ^^^^^^^^^^

worse


> Hopefully this is nothing serious,
> regards;

actually it's very serious, something is scribbling all over your
memory, it's just a matter of time before that overwrites something
important on your filesystem, and then you have a high risk of losing
most of your data.

However, since  you're using 2 proprietary kernel modules, you really
ought to contact the vendors for those modules for support; they're a
very likely cause for problems
(for example, these two are the cause for the number 1, 2, 5 and 7 of
the top 10 kernel oopses/crashes for the last week)



> 


-- 
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/