Closed Bug 686107 Opened 12 years ago Closed 12 years ago

Crash [@ JSC::MacroAssemblerCodePtr::executableAddress()]


(Core :: JavaScript Engine, defect)

Not set



Tracking Status
firefox9 + fixed
firefox10 + fixed
status1.9.2 --- unaffected


(Reporter: decoder, Assigned: bhackett1024)



(Keywords: crash, regression, testcase, Whiteboard: [sg:critical?][qa-])

Crash Data


(1 file)

The following test crashes on mozilla-central revision d078623f7875 (options -m -n -a), tested on 64 bit:

function testKeyTransitions() {
  var i, key, result, message;
  var array = [];
  for (i = 0; i != 10; i++) {
    key = (i < 3) ? 'pop' : (/\u009e\u0029/g );

Looks like a null-pointer deref, but s-s to be sure:

==39098== Invalid read of size 8
==39098==    at 0x4423CC: JSC::MacroAssemblerCodePtr::executableAddress() const (MacroAssemblerCodeRef.h:150)
==39098==    by 0x76FAF1: JSC::RepatchBuffer::RepatchBuffer(JSC::MacroAssemblerCodeRef const&) (RepatchBuffer.h:54)
==39098==    by 0x76FBD6: js::mjit::ic::Repatcher::Repatcher(js::mjit::JITScript*) (ICRepatcher.h:64)
==39098==    by 0x77806C: js::mjit::ic::BaseIC::disable(JSContext*, char const*, void*) (PolyIC.cpp:2233)
==39098==    by 0x77830A: js::mjit::ic::GetElementIC::disable(JSContext*, char const*) (PolyIC.cpp:2290)
==39098==    by 0x77AF86: js::mjit::ic::GetElementIC::update(js::VMFrame&, JSContext*, JSObject*, js::Value const&, jsid, js::Value*) (PolyIC.cpp:2757)
==39098==    by 0x77B131: js::mjit::ic::CallElement(js::VMFrame&, js::mjit::ic::GetElementIC*) (PolyIC.cpp:2788)
==39098==    by 0x6DF341: ??? (MethodJIT.cpp:153)
==39098==    by 0x6DF5DB: js::mjit::EnterMethodJIT(JSContext*, js::StackFrame*, void*, js::Value*, bool) (MethodJIT.cpp:884)
==39098==    by 0x6DF800: CheckStackAndEnterMethodJIT(JSContext*, js::StackFrame*, void*, bool) (MethodJIT.cpp:945)
==39098==    by 0x6DF950: js::mjit::JaegerShotAtSafePoint(JSContext*, void*, bool) (MethodJIT.cpp:972)
==39098==    by 0x502554: js::Interpret(JSContext*, js::StackFrame*, js::InterpMode) (jsinterp.cpp:2206)
==39098==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
Brian, can you take a look at this to see if it's a vulnerability?
Here's a bisect for the regressing changeset (possibly inaccurate):

The first bad revision is:
changeset:   76087:d763fda00eb9
user:        Brian Hackett
date:        Mon Aug 01 09:09:39 2011 -0700
summary:     [INFER] Only allow expansion of all inline frames in a compartment, bug 675251.

However, this test no longer reproduces on mozilla-central tip. Here's a bisect for a possible fix:

The first good revision is:
changeset:   77145:b961a248e94d
user:        Brian Hackett
date:        Sat Sep 17 19:31:33 2011 -0700
summary:     [INFER] Reapply f1c585415dd4 7c89b0ff453d 19794de530f1 (bug 686000).

Not sure if this is really fixed though, could also be that the second changeset just breaks the test. I guess Brian can figure that out :)

I also tested the latest aurora JS shell and cannot reproduce there.
Attached patch patchSplinter Review
Sorry, missed this bug when it was first filed.

Recompilation bug under ic::CallElement, if js_InternNonIntElementId triggers recompilation then we would still try to disable the IC afterwards.  ic::GetElement already does the right thing, I don't know why I didn't fix this when I fixed that one.
Assignee: general → bhackett1024
Attachment #564846 - Flags: review?(dvander)
Whiteboard: js-triage-needed
Attachment #564846 - Flags: review?(dvander) → review+
I made this sg:critical? because bug 692065 is a duplicate of this and shows use-after-free with invalid reads/writes so this could be exploitable.
Whiteboard: [sg:critical?]
Attachment #564846 - Flags: approval-mozilla-aurora?
Attachment #564846 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Trigger happy. I approved this and it hasn't hit m-c yet. Please hold off on landing this until it's made a cycle or three on m-c with no fallout.
Closed: 12 years ago
Resolution: --- → FIXED
I'm assuming this doesn't affect Firefox 8?
Keywords: regression
Target Milestone: --- → mozilla10
(In reply to Daniel Veditz from comment #9)
> I'm assuming this doesn't affect Firefox 8?

No, this doesn't.
Oops, not sure how I reset those bits.
Target Milestone: --- → mozilla9
Christian, can you please verify if this is fixed?
Whiteboard: [sg:critical?] → [sg:critical?][qa-]
Verified fixed on Firefox 9 and 10.
Group: core-security
Automatically extracted testcase for this bug was committed:
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.