RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

/var/run/virt-who.pid is world-writable

Version-Release number of selected component (if applicable):

RHEL 6.7 running virt-who-0.12-10.el6.noarch

How reproducible:

Always

Steps to Reproduce:
1).Install and Configure virt-who on a server in a VM environment.
2. Start virt-who service
3. Check for the permissions of the PID file created.

Actual results:

PID File created by virt-who is world writable.

Expected results:

PID File created by virt-who should not be world writable.

Reference Case # 01582525

Fixed upstream:

https://github.com/virt-who/virt-who/commit/4ddbb759cace9c2c31aec021cdb157712d46b56c

Fixed in virt-who-0.16-5.el6.

Checked it on virt-who-0.16-5.el6.noarch. the authority has update to 600. 
Can we modify it to 644?
[root@hp-z220-07 run]# ll /var/run/virt-who.pid
-rw-------. 1 root root 4 Mar  1 16:46 /var/run/virt-who.pid

Is there any reason why it should be 644? Why should non-root processes be able to read virt-who PID?

No special reason, I think the pid is not secret and other related service also show 644. Anyway, I will verify it.
[root@intel-piketon-01 ~]# ll /var/run/libvirtd.pid
-rw-r--r--. 1 root root 5 Mar 16 02:27 /var/run/libvirtd.pid

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-0859.html