Several segmentation fault occurred during check, should I be concerned?

[brlin-tw]

Running docker-compose up after cloning the repo prints:

Creating spectre-meltdown-checker ... done
Attaching to spectre-meltdown-checker
spectre-meltdown-checker    | Spectre and Meltdown mitigation detection tool v0.45
spectre-meltdown-checker    | 
spectre-meltdown-checker    | Checking for vulnerabilities on current system
spectre-meltdown-checker    | Kernel is Linux 5.13.0-37-generic #42-Ubuntu SMP Tue Mar 15 14:34:06 UTC 2022 x86_64
spectre-meltdown-checker    | CPU is Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
spectre-meltdown-checker    | Segmentation fault (core dumped)

spectre-meltdown-checker    | Segmentation fault (core dumped)

spectre-meltdown-checker    | Segmentation fault (core dumped)
spectre-meltdown-checker    | Segmentation fault (core dumped)
spectre-meltdown-checker    | Segmentation fault (core dumped)
spectre-meltdown-checker    | Segmentation fault (core dumped)
spectre-meltdown-checker    | Segmentation fault (core dumped)
spectre-meltdown-checker    | Segmentation fault (core dumped)
spectre-meltdown-checker    | 
spectre-meltdown-checker    | Hardware check
spectre-meltdown-checker    | * Hardware support (CPU microcode) for mitigation techniques
stripped...

Full output: docker_compose_up.out.txt

Issue is not reproduced when spectre-meltdown-checker.sh is run directly in the host system.

[speed47]

I can't reproduce this on my system. Could you try to run the script again with the -v -v options? You'll need to modify the dockerfile entrypoint:

ENTRYPOINT ["/check/spectre-meltdown-checker.sh","-v","-v"]

This should give a hint as to what tool crashes exactly in your case

[brlin-tw]

Here you are: docker-compose_up.out.txt

spectre-meltdown-checker    | (debug) try_decompress: magic for unlzma found at offset 10216274:xxx
spectre-meltdown-checker    | Segmentation fault (core dumped)

Seems to be unlzma cannot handle some data, note that I am unable to reproduce this issue as well using the docker branch so it is probably fixed in the later release of the alpine image.

Also, although not seems to be related:

spectre-meltdown-checker    | (debug) variables at end of script: (stripped)
spectre-meltdown-checker    | base64: unrecognized option: w
spectre-meltdown-checker    | BusyBox v1.27.2 (2018-06-06 09:08:44 UTC) multi-call binary.
spectre-meltdown-checker    | 
spectre-meltdown-checker    | Usage: base64 [-d] [FILE]
spectre-meltdown-checker    | 
spectre-meltdown-checker    | Base64 encode or decode FILE to standard output
spectre-meltdown-checker    |  -d  Decode data
spectre-meltdown-checker    |