Crash in [@ fstatat64_time64_statx]
Categories
(Core :: Security: Process Sandboxing, defect)
Tracking
()
People
(Reporter: mccr8, Assigned: jld)
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
Crash report: https://crash-stats.mozilla.org/report/index/1280b7f1-3453-477c-a95a-d2efc0231130
Reason: SIGSYS / SYS_SECCOMP
Top 10 frames of crashing thread:
0 ld-linux.so.2 fstatat64_time64_statx sysdeps/unix/sysv/linux/fstatat64.c:58
0 ld-linux.so.2 __GI___fstatat64_time64 sysdeps/unix/sysv/linux/fstatat64.c:158
1 ld-linux.so.2 __fstat64_time64 sysdeps/unix/sysv/linux/fstat64.c:35
2 ld-linux.so.2 _dl_get_file_id sysdeps/posix/dl-fileid.h:37
2 ld-linux.so.2 _dl_map_object_from_fd elf/elf/dl-load.c:968
3 ld-linux.so.2 _dl_map_object elf/elf/dl-load.c:2272
4 ld-linux.so.2 dl_open_worker_begin elf/elf/dl-open.c:534
5 ld-linux.so.2 _dl_catch_exception elf/elf/dl-catch.c:237
6 ld-linux.so.2 dl_open_worker elf/elf/dl-open.c:782
7 ld-linux.so.2 _dl_catch_exception elf/elf/dl-catch.c:237
Lots of crashes, but mostly from a single installation. mozilla::gmp::GMPLoader::Load() is farther up the stack.
| Assignee | ||
Comment 1•1 year ago
|
||
Obvious bug is obvious; we're not being polite about statx in the non-broker case. Should be a simple fix.
| Assignee | ||
Comment 2•1 year ago
|
||
STR appears to be any use of media plugins on 32-bit x86 with a recent glibc (not sure exactly how recent but Debian unstable is). Even clearkey crashes, so the in-tree EME tests reproduce this.
If we're still supporting 32-bit platforms in 2038 we'll need to actually handle statx, but for now it should be fine to force fallback.
| Assignee | ||
Comment 3•1 year ago
|
||
Testing note: this bug seems to break all GMP plugins on 32-bit x86,
including clearkey, so the regular EME tests would provide coverage, but
we're not testing that platform at all in CI anymore, let alone with a
new enough glibc. And testing this directly is difficult because our
sandbox tests run with crash-on-error mode turned off, and in that case
it just fails with ENOSYS both before and after.
Comment 5•1 year ago
|
||
| bugherder | ||
Comment 6•1 year ago
|
||
Sounds like uplifting this to Beta and ESR would be a good idea. Grafts cleanly to both.
| Assignee | ||
Comment 7•1 year ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #6)
Sounds like uplifting this to Beta and ESR would be a good idea. Grafts cleanly to both.
Normally yes, and thanks for suggesting it, but: non-Nightly builds have MOZ_SANDBOX_CRASH_ON_ERROR off by default, so they won't crash and the syscall will fail with ENOSYS, which is also the behavior after this patch. Low risk but effectively no benefit, so I don't think it's worth uplifting.
I've flagged the other branches as unaffected because that seemed more accurate than wontfix (although they would be affected if built as Nightly).
Updated•1 year ago
|
Description
•