[PR #7066] bugfix: error on invalid syscall name in seccomp #6300

New issue

Open

opened 2026-05-05 10:54:23 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 10:54:23 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/7066
Author: @kmk3
Created: 2/17/2026
Status: 🔄 Open

Base: master ← Head: fix-seccomp-invalid-syscall

📝 Commits (1)

79c43a5 bugfix: error on invalid syscall name in seccomp

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 src/lib/syscall.c (+4 -0)

📄 Description

Currently, an error is produced when an invalid syscall group is used:

$ firejail --quiet --seccomp.drop=@clock /bin/true
$ firejail --quiet --seccomp.drop=@foo /bin/true
Error fseccomp: unknown syscall group @foo

But not when an invalid syscall name is used (resulting in it being
silently ignored by firejail).

Make sure to also fail when that happens.

Before:

$ firejail --quiet --seccomp.drop=uname /bin/true
$ firejail --quiet --seccomp.drop=foo /bin/true

After:

$ firejail --quiet --seccomp.drop=uname /bin/true
$ firejail --quiet --seccomp.drop=foo /bin/true
Error fseccomp: invalid syscall list entry foo

Misc: From a cursory glance, this appears to have been an issue since
the syscall_process_name() function was introduced on commit 322ce2cdc
("seccomp rework", 2016-11-06).

Fixes #2931.

Reported-by: @aoand
Reported-by: @cobratbq

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/7066 **Author:** [@kmk3](https://github.com/kmk3) **Created:** 2/17/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `fix-seccomp-invalid-syscall` --- ### 📝 Commits (1) - [`79c43a5`](https://github.com/netblue30/firejail/commit/79c43a5381b2801a53108baefe04817246279080) bugfix: error on invalid syscall name in seccomp ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/syscall.c` (+4 -0) </details> ### 📄 Description Currently, an error is produced when an invalid syscall group is used: $ firejail --quiet --seccomp.drop=@clock /bin/true $ firejail --quiet --seccomp.drop=@foo /bin/true Error fseccomp: unknown syscall group @foo But not when an invalid syscall name is used (resulting in it being silently ignored by firejail). Make sure to also fail when that happens. Before: $ firejail --quiet --seccomp.drop=uname /bin/true $ firejail --quiet --seccomp.drop=foo /bin/true After: $ firejail --quiet --seccomp.drop=uname /bin/true $ firejail --quiet --seccomp.drop=foo /bin/true Error fseccomp: invalid syscall list entry foo Misc: From a cursory glance, this appears to have been an issue since the `syscall_process_name()` function was introduced on commit 322ce2cdc ("seccomp rework", 2016-11-06). Fixes #2931. Reported-by: @aoand Reported-by: @cobratbq --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

gitea-mirror added the

pull-request

label 2026-05-05 10:54:23 -06:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#6300

No description provided.

Rows
Columns