Skip to contentSkip to conversation

Linux 2.4.28-rc4

DISCUSSION O.Sezer 5 participants 7 messages Nov 17, 2004 – Nov 19, 2004

lore
Share & tools
lore

O.Sezer

author
#0 lore raw
Quoted 2 lines

Jakub Jelínek:
o binfmt_elf: handle p_filesz == 0 on PT_INTERP section

Another FYI: There were two successive binfmt_elf 2.6-backports posted by Barry Nathan here; "ELF fixes for executables with huge BSS":

http://marc.theaimsgroup.com/?t=109850369800001&r=1&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=109850420711579&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=109850420729735&w=2

but it may be too late for 2.4.28.

Ozkan Sezer

#1 lore raw
Quoted 11 lines · O.Sezer
Quoted 2 lines

Jakub Jelínek:
o binfmt_elf: handle p_filesz == 0 on PT_INTERP section

Another FYI: There were two successive binfmt_elf 2.6-backports posted by Barry Nathan here; "ELF fixes for executables with huge BSS":

http://marc.theaimsgroup.com/?t=109850369800001&r=1&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=109850420711579&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=109850420729735&w=2

but it may be too late for 2.4.28.

Marcelo and I discussed this via private e-mail; it's in the queue for 2.4.29-pre. I think in the end we both agreed that it's too late in the 2.4.28 cycle to include these patches.

-Barry K. Nathan <[email protected]>

#2 lore raw
Quoted 6 lines

Marcelo and I discussed this via private e-mail; it's in the queue for 2.4.29-pre. I think in the end we both agreed that it's too late in the
2.4.28 cycle to include these patches.

-Barry K. Nathan <[email protected]>

Why such a decision ?

Do you think that it is not exploitable or at least not in a short time ?

I don't think 2.4.29 will see the light in a short time so, unless there are serious problems arising from these patches (and 2.6 should be affected too), I think that for the sake of security it may be worthy and clever includind these patches (and delay 2.4.28 for some days...)

M$ is waiting for a gold occasion to shot on linux.
A known buffer overflow, not patched soon, may be used against linux and, what interest me more, we could avoid updating kernels on tons pf production servers for something which could be patched before.

Massimo Cetra

#3 lore raw
Quoted 4 lines · * Massimo Cetra ([email protected]) wrote:

I don't think 2.4.29 will see the light in a short time so, unless there are serious problems arising from these patches (and 2.6 should be affected too), I think that for the sake of security it may be worthy and clever includind these patches (and delay 2.4.28 for some days...)

2.4.28 is already out.

thanks,
-chris

Signature · 1 line
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net
#4 lore raw
Quoted 10 lines · * Massimo Cetra ([email protected]) wrote:
Quoted 2 lines

I don't think 2.4.29 will see the light in a short time so, unless there are serious problems arising from these patches (and

2.6 should

Quoted 2 lines

be affected too), I think that for the sake of security it may be worthy and clever includind these patches (and delay 2.4.28

for some

Quoted 1 line

days...)

2.4.28 is already out.

Too much work for me.
Sorry -__-

max

#6 lore raw
In reply to Barry K. Nathan
Quoted 11 lines · Barry K. Nathan
Quoted 10 lines · O.Sezer
Quoted 2 lines

Jakub Jelínek:
o binfmt_elf: handle p_filesz == 0 on PT_INTERP section

Another FYI: There were two successive binfmt_elf 2.6-backports posted by Barry Nathan here; "ELF fixes for executables with huge BSS":

http://marc.theaimsgroup.com/?t=109850369800001&r=1&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=109850420711579&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=109850420729735&w=2

Quoted 5 lines
Quoted 1 line

but it may be too late for 2.4.28.

Marcelo and I discussed this via private e-mail; it's in the queue for 2.4.29-pre. I think in the end we both agreed that it's too late in the 2.4.28 cycle to include these patches.

Yep - they will be in 2.4.29pre.

Thanks guys!

#5 lore raw
In reply to Massimo Cetra
Quoted 3 lines · Massimo Cetra

Why such a decision ?

Do you think that it is not exploitable or at least not in a short time ?

As far as I can tell, the only damage an exploit could do is to crash *itself*; unless I'm mistaken, any "exploit" would not be able to use either of these bugs to do any other mischief. I guess that's a long way of saying, I don't think it's exploitable.

-Barry K. Nathan <[email protected]>