On scrivano.org, locate the post about hiding the current process executable file. Explain the core mechanism of the CVE-2019-5736 vulnerability discussed in the article. Describe the general approach of the proposed kernel solution to address this, and state why it's considered a non-breaking change.
Navigate to the 'hide the current process executable file' post on scrivano.org. Identify how the CVE-2019-5736 vulnerability allowed attackers to escape containers. Locate the description of the proposed kernel solution. Determine the general effect of this solution on process access to its executable. Find the reason why this change is considered non-breaking.
Explain that the CVE-2019-5736 vulnerability allowed attackers to overwrite the container runtime executable file on the host by exploiting the `/proc/self/exe` file. State that the proposed solution is a new kernel option that makes any access to `/proc/self/exe` always return `EPERM`. Explain that this prevents a process from accessing its own executable file. State that the change is non-breaking because programs must opt-in to use the feature, and it does not affect programs that don't use it.