Skip to content

virtiofsd: stay under fs.file-max sysctl limit (CVE-2020-10717)

Stefan Hajnoczi qemu-devel virtio-fs 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v2 Latest2 patches 1 replyIn review

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2virtiofsd: add --rlimit-nofile=NUM optiontools/virtiofsd/fuse_lowlevel.h tools/virtiofsd/helper.c tools/virtiofsd/passthrough_ll.c+32 -140 replies
2/2virtiofsd: stay below fs.file-max sysctl value (CVE-2020-10717)tools/virtiofsd/helper.c+25 -10 replies

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchDr. David Alan Gilbert
1/2R-b
2/2R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v2 thread

Cover letter [PATCH v2 0/2] virtiofsd: stay under fs.file-max sysctl limit (CVE-2020-10717)

This patch series introduces the --rlimit-nofile=NUM option for setting the number of open files on the virtiofsd process. This gives users and management tools more control over resource limits.

Previously it was possible for FUSE clients on machines with less than ~10 GB of RAM to exhaust the system-wide open file limit. This is a denial of service attack against other processes running on the host.

This patch series updates the default RLIMIT_NOFILE calculation to take the fs.file-max sysctl value into account. This solves the fs.file-max DoS.

Stefan Hajnoczi (2):
virtiofsd: add --rlimit-nofile=NUM option
virtiofsd: stay below fs.file-max sysctl value (CVE-2020-10717)

 tools/virtiofsd/fuse_lowlevel.h  |  1 +
 tools/virtiofsd/helper.c         | 47 ++++++++++++++++++++++++++++++++
 tools/virtiofsd/passthrough_ll.c | 22 ++++++---------
 3 files changed, 56 insertions(+), 14 deletions(-)
Signature · 1 line
2.25.3