<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ebiggers</author><text>AFAICS, this was exposed by the addition of sockfs_setattr() in v4.10.  So it&amp;#x27;s incorrect to claim that kernels older than that are vulnerable, even though the code being fixed was older.&lt;p&gt;Also, note that there may not actually be a proof-of-concept exploit yet, beyond a reproducer causing a KASAN splat.  When people request a CVE for a use-after-free bug they usually just assume that code execution may be possible.  (Exploits can be very creative.)</text><parent_chain></parent_chain></comment><story><title>Linux Kernel Through 4.20.10 Found Vulnerable to Arbitrary Code Execution</title><url>https://coocoor.com/advisory/cve/CVE-2019-8912</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>sargun</author><text>How does this use-after-free turn into an arbitrary code execution vuln? I don&amp;#x27;t see any jmp to the pointer?</text><parent_chain></parent_chain></comment><story><title>Linux Kernel Through 4.20.10 Found Vulnerable to Arbitrary Code Execution</title><url>https://coocoor.com/advisory/cve/CVE-2019-8912</url></story>