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  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]
Date:	Fri, 31 Jan 2014 18:12:54 -0800
From:	Andrew Morton <>
To:	"Pearson, Greg" <>
Cc:	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>
Subject: Re: [PATCH] vmcore: prevent PT_NOTE p_memsz overflow during header

On Sat, 1 Feb 2014 01:07:29 +0000 "Pearson, Greg" <> wrote:

> As far as I know the only consequence of dropping a PT_NOTE entry is 
> that it would not be available in the crash dump for use in debugging. 
> I'm not sure how important this data might be for triage. I'm guessing 
> that in cases where one of these strange PT_NOTE entries shows up with a 
> size that causes an overflow it probably isn't even a real PT_NOTE entry 
> so dropping it won't matter, but that's a guess at this point since I'm 
> still trying to figure out how the bogus entries were created.

Can we detect the crazy-huge notes, skip them and then proceed with
the following sanely-sized ones?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists