github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #2700] firemon error: recv: No buffer space available #1699

New issue
Closed
opened 2026-05-05 08:21:25 -06:00 by gitea-mirror · 2 comments
gitea-mirror commented 2026-05-05 08:21:25 -06:00
Owner
Copy link

Originally created by @smitsohu on GitHub (May 16, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2700

This looks like a non-deterministic bug.

In one terminal run sudo firemon, then start a sandbox:

smitsohu@smitsohu:~$ sudo firemon
13:58:01 uid (1000:0) 22759 (root) NEW SANDBOX: firejail 
13:58:01 exec 22759 (smitsohu) firejail 
13:58:01 fork 22759 (smitsohu) firejail 
	child 22760 firejail 
13:58:01 fork 22759 (smitsohu) firejail 
	child 22761 firejail 
13:58:01 exit 22761 (smitsohu)
13:58:01 fork 22760 (smitsohu) firejail 
	child 22762 firejail 
13:58:01 gid (1000:1000) 22762 (smitsohu) firejail 
13:58:01 uid (1000:1000) 22762 (smitsohu) firejail 
13:58:01 exec 22762 (smitsohu) /run/firejail/lib/fseccomp protocol build unix,inet,inet6 /run/firejail/mnt/seccomp/seccomp.protocol 
13:58:01 exit 22762 (smitsohu)
recv: No buffer space available
firemon: procevent.c:499: procevent: Assertion `0' failed.
Aborted

If the code is instrumented with fsanitize=undefined, this is the result:

procevent.c:288:19: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 00 00 00 00  03 00 00 00 d1 a7 de ff  ea d3 00 00 00 00 00 00  00 00 00 00 00 00 00 00
              ^ 
procevent.c:293:34: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 01 00 00 00  00 00 00 00 9a f8 58 a3  eb d3 00 00 f3 08 00 00  f3 08 00 00 38 3c 00 00
              ^ 
procevent.c:294:34: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 01 00 00 00  00 00 00 00 9a f8 58 a3  eb d3 00 00 f3 08 00 00  f3 08 00 00 38 3c 00 00
              ^ 
procevent.c:296:10: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 01 00 00 00  00 00 00 00 9a f8 58 a3  eb d3 00 00 f3 08 00 00  f3 08 00 00 38 3c 00 00
              ^ 
procevent.c:310:10: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 02 00 00 00  02 00 00 00 86 e2 dd a3  eb d3 00 00 38 3c 00 00  38 3c 00 00 00 00 00 00
              ^ 
procevent.c:321:34: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 00 00 00 80  02 00 00 00 c7 34 f4 a9  eb d3 00 00 3b 3c 00 00  39 3c 00 00 00 00 00 00
              ^ 
procevent.c:322:34: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 00 00 00 80  02 00 00 00 c7 34 f4 a9  eb d3 00 00 3b 3c 00 00  39 3c 00 00 00 00 00 00
              ^ 
procevent.c:325:10: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 00 00 00 80  03 00 00 00 7d af fc a9  eb d3 00 00 39 3c 00 00  39 3c 00 00 00 00 00 00
              ^ 
procevent.c:370:10: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment
0x7ffea9197bc4: note: pointer points here
  28 00 00 00 80 00 00 00  01 00 00 00 ba 06 bb 73  ef d3 00 00 65 3c 00 00  65 3c 00 00 00 00 00 00
              ^ 

and so on ...
Originally created by @smitsohu on GitHub (May 16, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2700 This looks like a non-deterministic bug. In one terminal run `sudo firemon`, then start a sandbox: ``` smitsohu@smitsohu:~$ sudo firemon 13:58:01 uid (1000:0) 22759 (root) NEW SANDBOX: firejail 13:58:01 exec 22759 (smitsohu) firejail 13:58:01 fork 22759 (smitsohu) firejail child 22760 firejail 13:58:01 fork 22759 (smitsohu) firejail child 22761 firejail 13:58:01 exit 22761 (smitsohu) 13:58:01 fork 22760 (smitsohu) firejail child 22762 firejail 13:58:01 gid (1000:1000) 22762 (smitsohu) firejail 13:58:01 uid (1000:1000) 22762 (smitsohu) firejail 13:58:01 exec 22762 (smitsohu) /run/firejail/lib/fseccomp protocol build unix,inet,inet6 /run/firejail/mnt/seccomp/seccomp.protocol 13:58:01 exit 22762 (smitsohu) recv: No buffer space available firemon: procevent.c:499: procevent: Assertion `0' failed. Aborted ``` If the code is instrumented with `fsanitize=undefined`, this is the result: ``` procevent.c:288:19: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 00 00 00 00 03 00 00 00 d1 a7 de ff ea d3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ procevent.c:293:34: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 01 00 00 00 00 00 00 00 9a f8 58 a3 eb d3 00 00 f3 08 00 00 f3 08 00 00 38 3c 00 00 ^ procevent.c:294:34: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 01 00 00 00 00 00 00 00 9a f8 58 a3 eb d3 00 00 f3 08 00 00 f3 08 00 00 38 3c 00 00 ^ procevent.c:296:10: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 01 00 00 00 00 00 00 00 9a f8 58 a3 eb d3 00 00 f3 08 00 00 f3 08 00 00 38 3c 00 00 ^ procevent.c:310:10: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 02 00 00 00 02 00 00 00 86 e2 dd a3 eb d3 00 00 38 3c 00 00 38 3c 00 00 00 00 00 00 ^ procevent.c:321:34: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 00 00 00 80 02 00 00 00 c7 34 f4 a9 eb d3 00 00 3b 3c 00 00 39 3c 00 00 00 00 00 00 ^ procevent.c:322:34: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 00 00 00 80 02 00 00 00 c7 34 f4 a9 eb d3 00 00 3b 3c 00 00 39 3c 00 00 00 00 00 00 ^ procevent.c:325:10: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 00 00 00 80 03 00 00 00 7d af fc a9 eb d3 00 00 39 3c 00 00 39 3c 00 00 00 00 00 00 ^ procevent.c:370:10: runtime error: member access within misaligned address 0x7ffea9197bc4 for type 'struct proc_event', which requires 8 byte alignment 0x7ffea9197bc4: note: pointer points here 28 00 00 00 80 00 00 00 01 00 00 00 ba 06 bb 73 ef d3 00 00 65 3c 00 00 65 3c 00 00 00 00 00 00 ^ and so on ... ```
gitea-mirror 2026-05-05 08:21:25 -06:00
  • closed this issue
  • added the
    bug
         label
gitea-mirror commented 2026-05-05 08:21:28 -06:00
Author
Owner
Copy link

@smitsohu commented on GitHub (May 16, 2019):

I should add that I'm seeing the UBSan messages only on one machine, I cannot reproduce them for example in my virtual machines.

<!-- gh-comment-id:493244473 --> @smitsohu commented on GitHub (May 16, 2019): I should add that I'm seeing the UBSan messages only on one machine, I cannot reproduce them for example in my virtual machines.
gitea-mirror commented 2026-05-05 08:21:29 -06:00
Author
Owner
Copy link

@SkewedZeppelin commented on GitHub (May 16, 2019):

I've seen this error before from firemon, but haven't in a while.

<!-- gh-comment-id:493245864 --> @SkewedZeppelin commented on GitHub (May 16, 2019): I've seen this error before from firemon, but haven't in a while.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear 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

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
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
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#1699
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?