Home Business IT Open Source Kernel developer criticises Linux over security
Kernel developer criticises Linux over security Featured

A senior Linux kernel developer has pointed to an instance of what he calls a lax approach to security in the Linux kernel, citing the case of a serious vulnerability that is now more than a month old and is yet to be fixed.

Jonathan Corbet (pictured above), who is also the editor of the Linux Weekly News website, described in an article how a flaw in the kernel, which was initially discussed on a private mailing list, had been made public with a posting by a developer named Oleg Nesterov.

According to Corbet, the vulnerability in question would permit the running of arbitrary code in kernel mode.

"It seems that the Linux implementation of the ptrace() system call contains a race condition: a traced process's registers can be changed in a way that causes the kernel to restore that process's stack contents to an arbitrary location," he wrote.

Corbet raised the issue in the context of a discussion of other kernel vulnerabilities and criticism, by a security-oriented firm Trustwave, of the way these were handled. The firm claimed that it took nearly three years to patch two flaws, claims which Corbet contested.

But in the case of the vulnerability that he himself cited, Corbet said the bug was known to be a serious one from the outset and that one of the developers who reported it had also created exploit code to demonstrate its severity.

He said that though the public discussion of this bug was nearly a month old at the time of writing - his article appeared on February 19 - and had been discussed for a while before that privately, no distributor had taken a step to issue a fix.

Nesterov works for Red Hat and Corbet quoted another developer as asking why this company had not handled the issue as it should have been.

"Distributors knew about the problem and had time to respond to it — but that response did not happen in a timely manner," Corbet concluded.

"The ptrace() problem will certainly be straightened out in less than three years, but that still may not be a reason for pride. Users should not be left wondering what the situation is (at least) one month after distributors know about a serious vulnerability."

WEBINAR 26/27th May

Thinking of deploying Business Intelligence (BI)? So are your competitors.

And the most important, fundamental, tool for delivering your BI information to your users? Dashboards.

THIS IS ONE NOT TO MISS SO REGISTER NOW

DON'T MISS OUT - REGISTER NOW!

FREE WHITEPAPER - RISKS OF MOVING DATABASES TO VMWARE

VMware changed the rules about the server resources required to keep a database responding

It's now more difficult for DBAs to see interaction between the database and server resources

This whitepaper highlights the key differences between performance management between physical and virtual servers, and maps out the five most common trouble spots when moving production databases to VMware

1. Innacurate metrics
2. Dynamic resource allocation
3. No control over Host Resources
4. Limited DBA visibility
5. Mutual ignorance

Don't move your database to VMware before learning about these potential risks, download this FREE Whitepaper now!

DOWNLOAD!

Sam Varghese

website statistics

A professional journalist with decades of experience, Sam for nine years used DOS and then Windows, which led him to start experimenting with GNU/Linux in 1998. Since then he has written widely about the use of both free and open source software, and the people behind the code. His personal blog is titled Irregular Expression.

Connect

 

 

 

 

Join the iTWire Community and be part of the latest news, invites to exclusive events, whitepapers and educational materials and oppertunities.
Why do I want to receive this daily update?
  • The latest features from iTWire
  • Free whitepaper downloads
  • Industry opportunities