-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-9.8, rhel-10.2
-
None
-
None
-
None
-
rhel-idm-uah
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
When opening corrupted file, should get Access Denied. Instead, the file is not neither opened or scanned.
With samba 4.22:
smbclient //127.0.0.1/virusfilter -U smbuser%... -c "open eicar.com.txt"
Failed to open file \eicar.com.txt. NT_STATUS_ACCESS_DENIED
With samba 4.23:
smbclient //127.0.0.1/virusfilter -U smbuser%... -c "open eicar.com.txt"
open file \eicar.com.txt: for read/write fnum 1
Errors from log:
[2025/11/07 09:15:40.395812, 0, pid=16490, effective(1001, 1001), real(1001, 0), class=virusfilter] ../../source3/modules/vfs_virusfilter_clamav.c:58(virusfilter_clamav_scan_init)
virusfilter_clamav_scan_init: clamd: Connecting to socket failed: /run/clamd.scan/clamd.sock: Protocol not supported
[2025/11/07 09:15:40.395860, 0, pid=16490, effective(1001, 1001), real(1001, 0), class=virusfilter] ../../source3/modules/vfs_virusfilter.c:1214(virusfilter_scan)
virusfilter_scan: Scan result: Error: /tmp/virusfilter/eicar.com.txt: Initializing scanner failed
clamd version is the same on both tested machines:
[root@client ~]# clamd --version
ClamAV 1.4.3/27815/Thu Nov 6 05:44:56 2025
What is the impact of this issue to you?
Please provide the package NVR for which the bug is seen:
samba-4.23.0-101.el10.x86_64
works with:
samba-4.22.4-6.el9_7.x86_64
samba-4.22.4-106.el10_1.x86_64