https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 06 Oct 2026 21:46:28 +0000 https://cve.radiocsirt.org/vuln/cve-2022-48801 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL</p> <p>If we fail to copy the just created file descriptor to userland, we try to clean up by putting back &#39;fd&#39; and freeing &#39;ib&#39;. The code uses put_unused_fd() for the former which is wrong, as the file descriptor was already published by fd_install() which gets called internally by anon_inode_getfd().</p> <p>This makes the error handling code leaving a half cleaned up file descriptor table around and a partially destructed &#39;file&#39; object, allowing userland to play use-after-free tricks on us, by abusing the still usable fd and making the code operate on a dangling &#39;file-&gt;private_data&#39; pointer.</p> <p>Instead of leaving the kernel in a partially corrupted state, don&#39;t attempt to explicitly clean up and leave this to the process exit path that&#39;ll release any still valid fds, including the one created by the previous call to anon_inode_getfd(). Simply return -EFAULT to indicate the error.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL</p> <p>If we fail to copy the just created file descriptor to userland, we try to clean up by putting back &#39;fd&#39; and freeing &#39;ib&#39;. The code uses put_unused_fd() for the former which is wrong, as the file descriptor was already published by fd_install() which gets called internally by anon_inode_getfd().</p> <p>This makes the error handling code leaving a half cleaned up file descriptor table around and a partially destructed &#39;file&#39; object, allowing userland to play use-after-free tricks on us, by abusing the still usable fd and making the code operate on a dangling &#39;file-&gt;private_data&#39; pointer.</p> <p>Instead of leaving the kernel in a partially corrupted state, don&#39;t attempt to explicitly clean up and leave this to the process exit path that&#39;ll release any still valid fds, including the one created by the previous call to anon_inode_getfd(). Simply return -EFAULT to indicate the error.</p> https://cve.radiocsirt.org/vuln/cve-2022-48801