Eric Paris

**Name of the Vulnerable Software and Affected Versions** Kube-proxy versions (affected versions not specified) **Description** The issue concerns Kube-proxy on Windows, which can unintentionally forward traffic to local processes listening on the same port (`spec.ports[*].port`) as a LoadBalancer Service. This occurs when the LoadBalancer controller does not set the `status.loadBalancer.ingress[].ip` field. Clusters where the LoadBalancer controller sets this field are unaffected. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions prior to 2.6.39 **Description** A double free vulnerability exists in the inotify subsystem of the Linux kernel, allowing local users to cause a denial of service, resulting in a system crash. This issue arises from incorrect attempts to create files. **Recommendations** For Linux kernel versions prior to 2.6.39, update to version 2.6.39 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Linux kernel version 2.6.18 **Description** The issue is related to the NFSv4 implementation in the Linux kernel, where it fails to properly clean up an inode when an O EXCL create fails. This can lead to files being created with insecure settings, such as setuid bits, potentially allowing local users to gain privileges. The problem is associated with the execution of the do open permission function, even when a create operation fails. **Recommendations** For Linux kernel version 2.6.18, consider restricting access to the NFSv4 functionality until a proper fix is applied, and ensure that all file creations are thoroughly audited to prevent insecure settings.