mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #7058] io_uring filtering #3471
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3471
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ssokolow on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/netblue30/firejail/issues/7058
Is your feature request related to a problem? Please describe.
To quote Jens Axboe's submission to enable BPF filtering of io_uring in Linux 7.0:
Describe the solution you'd like
Support applying BPF filters to io_uring to complement seccomp filters.
Describe alternatives you've considered
Nothing. I trust Jens when he says that this is motivated by a lack of alternatives other than blocking access to io_uring.
Environment
This should be irrelevant for this feature request, but since you asked for it...
uname -srm): Linux 6.8.0-88-generic x86_64lsb_release -a)firejail --version): firejail version 0.9.72If you use a development version of firejail, also the commit from which it:was compiled (
git rev-parse HEAD):@kmk3 commented on GitHub (Feb 10, 2026):
(Offtopic)
Note that we do not maintain that version of firejail:
Versions other than the latest usually have outdated profiles and may contain
bugs and security vulnerabilities that were fixed in later versions.
See also:
@ssokolow commented on GitHub (Feb 10, 2026):
I'm using the Kubuntu 24.04 LTS repo package of firejail. If there are security bugs, please do whatever the Flatpak people do to get their fixes into the http://security.ubuntu.com/ubuntu repo.
As for outdated profiles, I predominantly use a script I wrote named
sandboxifyto generate profiles for GOG.com games which don't depend on the core firejail.incfiles because I don't want updates to potentially break games. Wherever possible, I prefer Flatpak because it's much easier to further tighten the sandbox profiles on containerized apps. (Aflatpakifyfor my GOG games is under consideration.)@kmk3 commented on GitHub (Feb 10, 2026):
We are a small team and we only support the latest version.
If you are interested in maintaining and supporting an older version of
firejail, feel free to look in the commit log and RELNOTES for security-related
changes and apply them to your tree.
See also:
@ssokolow commented on GitHub (Feb 10, 2026):
I have far too much going on in my life to take on more responsibility. Again, please get in touch with the Ubuntu Firejail maintainer to see about getting them to do that.
As for the PPA, since firejail is suid, I'll put it on my TODO list to start looking into whether there's sufficient procedure in place to protect the PPA from introducing new attack surface.
Failing that, if I decide it's too big a risk, I'll probably ditch firejail and rejigger my
sandboxifyscript to generate launcher scripts for bubblewrap instead, on the assumption that, since Flatpak depends on it, it'll get more attention.Either way, this is all off-topic to the purpose of this feature request: A kernel commit got added to enable sandboxing of io_uring at finer granularity than "disable it".