From: Ralf Baechle DL5RB <ralf@linux-mips.org>
To: "Curt, WE7U" <archer@eskimo.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: Kernel NULL pointer vulnerability: AX.25 module
Date: Wed, 26 Aug 2009 18:16:30 +0100 [thread overview]
Message-ID: <20090826171630.GB26668@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0908141052000.9150@shell.eskimo.com>
On Fri, Aug 14, 2009 at 10:59:00AM -0700, Curt, WE7U wrote:
> FYI: My CentOS 5.x systems appear to be ok. CentOS 4.x systems are
> supposed to be vulnerable. My OpenSuSE 11.x systems appear to be
> vulnerable but I'm only running AX.25 on one machine and only
> occasionally. Note that there's a type in the net-pf-24 line below
> also. Read the LWM link or Google for additional info. --we7u
>
> ---------- Forwarded message ----------
> Date: Fri, 14 Aug 2009 14:24:39 +0200
> From: Marcus Moeller <mail@marcus-moeller.de>
> To: CentOS mailing list <centos@centos.org>
> Subject: [CentOS] Kernel NULL pointer vulnerability
>
> Hi all.
>
> Julien Tinnes and Tavis Ormandy from the Google Security Team have
> recently found a Linux kernel vulnerability which affects all 2.4 and
> 2.6 kernels since 2001 on all architectures. Please read the
> announcement on LWM: http://lwn.net/Articles/347006/ for further
> information about the vulnerability and the exploit which has been
> provided by Brad Spengler (you will find updates on his twitter site).
>
> The only workaroud that is known to me atm is to disable the affected
> kernel modules (which should be handled with care as some of them may
> provide necessary functionality in your operating environment):
>
> echo "alias net-pf-3 off # Amateur Radio AX.25
No. AX.25 had the .sendpage methode in its ax25_proto_ops so is not
vulnerable to this attack. The same is true for NETROM and ROSE and for
all kernel versions since the sendpage method was introduced in 2.4.4.
Which btw doesn't changes why AX.25 should not be used on mission
critical system. There is a sufficient number of locking issues in the
code that I recommend avoiding that. These issues can only result in
panic, hangs or malfunction of the protocol state engine or minor resource
wastage but no priviledge escalation afaics.
Ralf
prev parent reply other threads:[~2009-08-26 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 17:59 Kernel NULL pointer vulnerability: AX.25 module Curt, WE7U
2009-08-26 17:16 ` Ralf Baechle DL5RB [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090826171630.GB26668@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=archer@eskimo.com \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox