[CAN-2005-0204]: AMD64, allows local users to write to privileged IO ports via OUTS instruction
From: micah milano (micaho_at_gmail.com)
Date: 02/28/05
- Previous message: Jeff Mahoney: "Re: Help tracking down problem --- endless loop in __find_get_block_slow (now with the patch)"
- Next in thread: Chris Wright: "Re: [CAN-2005-0204]: AMD64, allows local users to write to privileged IO ports via OUTS instruction"
- Reply: Chris Wright: "Re: [CAN-2005-0204]: AMD64, allows local users to write to privileged IO ports via OUTS instruction"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 28 Feb 2005 15:27:13 -0600 To: linux-kernel@vger.kernel.org
Hello,
CAN-2005-0204 reads:
Linux kernel before 2.6.9, when running on the AMD64 and Intel EM64T
architectures, allows local users to write to privileged IO ports via
the OUTS instruction.
Although this says "before 2.6.9" this *includes* 2.6.8 (and 2.4.29)
as well as 2.6.9 and apparantly it includes 2.6.10 and soon to be
released 2.6.11 based on my browsing through the changelogs and not
seeing a mention of this, or that particular file being changed. I do
see that the particular function where this is located has changed
slightly, the patch still seems applicable.
Kernel 2.4.29 appears to have a similar vulnerability, although this
patch would not apply cleanly to that tree, but looks relatively
trivial to modify appropriately.
Apparantly this hole has not migrated upstream somehow and so I am
posting this message to find out where its at.
REDHAT:RHSA-2005:092
URL:http://www.redhat.com/support/errata/RHSA-2005-092.html
The RedHat bug associated with this is located at:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=148855
A patch to fix the problem is located here (also linked to the RedHat bug):
https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=110424&action=view
This apparantly only affects AMD64 and EM64T.
Thanks,
micah
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Jeff Mahoney: "Re: Help tracking down problem --- endless loop in __find_get_block_slow (now with the patch)"
- Next in thread: Chris Wright: "Re: [CAN-2005-0204]: AMD64, allows local users to write to privileged IO ports via OUTS instruction"
- Reply: Chris Wright: "Re: [CAN-2005-0204]: AMD64, allows local users to write to privileged IO ports via OUTS instruction"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- [RESUBMIT] [PATCH] [BUGFIX] sound/oss/es1371.c: Dont print joystick address before its set.
... Resubmit because of no feedback nor inclusion in the latest changelogs. ...
I'm not sure wether this patch qualifies for the patch monkey, ... The old code printed
the joystick address before it was set, ... send the line "unsubscribe linux-kernel"
in ... (Linux-Kernel) - Re: [PATCH 1/14] LinuxTV.org DVB driver update
... > match was the video lists. ... I just browsed thorugh the changelogs
at ... But I have just cut out your patch, ... send the line "unsubscribe linux-kernel"
in ... (Linux-Kernel) - [vm 5/6] convert users of remap_page_range() under sound/ to use remap_pfn_range()
... This patch converts all users of remap_page_rangeunder sound/ to use ... remap_pfn_range,
with the exception of maestro3 changelogs, which are ... changelogs are), regardless
of API changes. ... send the line "unsubscribe linux-kernel" in ... (Linux-Kernel) - Re: [parisc-linux] Re: [PATCH 3/9] mm: parisc pte atomicity
... using your own tmpalias area sounds much better than getting ... I've simply
not wrapped my head around the races, ... it looks like we agree that my patch is
necessary and valid as is; ... send the line "unsubscribe linux-kernel" in ... (Linux-Kernel) - Re: keyboard - was: Re: Linux 2.6.0-test4
... >> I was able to get the key unstuck by switching back and forth between ...
I rebuild my kernel including your patch; ... I'll get back to you once I verify
that the problem doesn't occur ... send the line "unsubscribe linux-kernel" in ...
(Linux-Kernel)