Darwin/XNU execute error

[T1 Oner]

I want to run syzkaller after looking at the Darwin/XNU manual.

(https://github.com/google/syzkaller/blob/master/docs/darwin/README.md)

Up to the Booting macOS via Qemu stage, it was confirmed that it worked successfully.

To perform the last step, "Fuzzing with Syzkaller", "syzkaller.cfg" was created and executed according to the manual, but the following error was confirmed.

What could be the problem?

go version : go version go1.20.1 darwin/amd64
Host macOS version : Ventura 13.2
Guest macOS version : Big sur 11.5 (same version as specified in the manual)

[T1 Oner]

Duplicate question below. sorry.

2023/02/27 19:54:00 SYZFATAL: failed to open ELF file /path/to/115/obj/kernel.kasan: bad magic number '[207 250 237 254]' in record at byte 0x0

2023년 2월 27일 월요일 오후 8시 18분 50초 UTC+9에 T1 Oner님이 작성:

[Aleksandr Nogikh]

Space, FYI

> --
> You received this message because you are subscribed to the Google Groups "syzkaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/20a0edd3-d0ab-468a-ab67-cc847eb419a9n%40googlegroups.com.

[T1 Oner]

What space? 

2023년 3월 6일 월요일 오후 7시 58분 16초 UTC+9에 nog...@google.com님이 작성:

[Patrick Meyer]

Smells like it could be a regression in our MachO binary parsing. We read the kernel to extract DWARF information. You get an error about ELF parsing at that point. The macos kernel won't be in ELF format though.

I don't have the setup to repro this at the moment. Can you try whether going back to d236a457274375e5273ac4e958722659929c469f fixes this problem for you?

- Space

 

To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/00ff53b0-78b9-460c-8479-232adabede23n%40googlegroups.com.

[T1 Oner]

Thank you for your late reply. However, even if I try as suggested above, the same error occurs. It seems that the kernel image is not an ELF file. Is there a way to solve it? I hope this helps!

2023년 3월 20일 월요일 오후 8시 9분 31초 UTC+9에 s...@google.com님이 작성:

[Space Meyer]

I tested this over the holiday. I reproduced this issue on head and narrowed the cause down to this commit, where we switched from symbolising reports via nm to golangs debug/elf. As the xnu kernel is a macho binary, this of course doesn't work.

I also confirmed my proposed workaround of going back to d236a457274375e5273ac4e958722659929c469f works. Please make sure you rebuild the syzkaller binaries.

To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/b77e6d71-bbf7-4562-9af1-a7d496cc9a77n%40googlegroups.com.