https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 14:14:32 +0000 https://cve.radiocsirt.org/vuln/bell-cve-2026-74522 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-74522 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090 certfr-2026-avi-1090 https://cve.radiocsirt.org/vuln/certfr-2026-avi-1090 https://cve.radiocsirt.org/vuln/euvd-2026-356411 EUVD-2026-356411 https://cve.radiocsirt.org/vuln/euvd-2026-356411 https://cve.radiocsirt.org/vuln/fkie_cve-2026-74522 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix use-after-free in __close_file_table_ids()</p> <p>A ksmbd_file can remain alive after logical close while another session holds a temporary reference obtained through ksmbd_lookup_fd_inode(). ksmbd_close_fd() currently marks the file closed and drops the idr-owned reference, but leaves the pointer published in the closing session&#39;s idr until the final reference is dropped.</p> <p>If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final() supplies the foreign session&#39;s file table to __ksmbd_close_fd(). The object is then freed without being removed from its owner&#39;s idr, and the owner session later dereferences the stale pointer during file-table teardown.</p> <p>Remove the volatile id from the owner&#39;s idr while ksmbd_close_fd() still holds that table&#39;s lock, and clear volatile_id before dropping the idr-owned reference. A later foreign final put then only performs physical destruction and cannot remove the object from the wrong table.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix use-after-free in __close_file_table_ids()</p> <p>A ksmbd_file can remain alive after logical close while another session holds a temporary reference obtained through ksmbd_lookup_fd_inode(). ksmbd_close_fd() currently marks the file closed and drops the idr-owned reference, but leaves the pointer published in the closing session&#39;s idr until the final reference is dropped.</p> <p>If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final() supplies the foreign session&#39;s file table to __ksmbd_close_fd(). The object is then freed without being removed from its owner&#39;s idr, and the owner session later dereferences the stale pointer during file-table teardown.</p> <p>Remove the volatile id from the owner&#39;s idr while ksmbd_close_fd() still holds that table&#39;s lock, and clear volatile_id before dropping the idr-owned reference. A later foreign final put then only performs physical destruction and cannot remove the object from the wrong table.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-74522 https://cve.radiocsirt.org/vuln/ghsa-r5jm-2247-f5r8 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix use-after-free in __close_file_table_ids()</p> <p>A ksmbd_file can remain alive after logical close while another session holds a temporary reference obtained through ksmbd_lookup_fd_inode(). ksmbd_close_fd() currently marks the file closed and drops the idr-owned reference, but leaves the pointer published in the closing session&#39;s idr until the final reference is dropped.</p> <p>If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final() supplies the foreign session&#39;s file table to __ksmbd_close_fd(). The object is then freed without being removed from its owner&#39;s idr, and the owner session later dereferences the stale pointer during file-table teardown.</p> <p>Remove the volatile id from the owner&#39;s idr while ksmbd_close_fd() still holds that table&#39;s lock, and clear volatile_id before dropping the idr-owned reference. A later foreign final put then only performs physical destruction and cannot remove the object from the wrong table.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ksmbd: fix use-after-free in __close_file_table_ids()</p> <p>A ksmbd_file can remain alive after logical close while another session holds a temporary reference obtained through ksmbd_lookup_fd_inode(). ksmbd_close_fd() currently marks the file closed and drops the idr-owned reference, but leaves the pointer published in the closing session&#39;s idr until the final reference is dropped.</p> <p>If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final() supplies the foreign session&#39;s file table to __ksmbd_close_fd(). The object is then freed without being removed from its owner&#39;s idr, and the owner session later dereferences the stale pointer during file-table teardown.</p> <p>Remove the volatile id from the owner&#39;s idr while ksmbd_close_fd() still holds that table&#39;s lock, and clear volatile_id before dropping the idr-owned reference. A later foreign final put then only performs physical destruction and cannot remove the object from the wrong table.</p> https://cve.radiocsirt.org/vuln/ghsa-r5jm-2247-f5r8 https://cve.radiocsirt.org/vuln/msrc_cve-2026-74522 msrc_CVE-2026-74522 https://cve.radiocsirt.org/vuln/msrc_cve-2026-74522 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74522 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in __close_file_table_ids() A ksmbd_file can remain alive after logical close while another session holds a temporary reference obtained through ksmbd_lookup_fd_inode(). ksmbd_close_fd() currently marks the file closed and drops the idr-owned reference, but leaves the pointer published in the closing session&#39;s idr until the final reference is dropped. If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final() supplies the foreign session&#39;s file table to __ksmbd_close_fd(). The object is then freed without being removed from its owner&#39;s idr, and the owner session later dereferences the stale pointer during file-table teardown. Remove the volatile id from the owner&#39;s idr while ksmbd_close_fd() still holds that table&#39;s lock, and clear volatile_id before dropping the idr-owned reference. A later foreign final put then only performs physical destruction and cannot remove the object from the wrong table.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 193 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in __close_file_table_ids() A ksmbd_file can remain alive after logical close while another session holds a temporary reference obtained through ksmbd_lookup_fd_inode(). ksmbd_close_fd() currently marks the file closed and drops the idr-owned reference, but leaves the pointer published in the closing session&#39;s idr until the final reference is dropped. If the foreign holder performs the final ksmbd_fd_put(), __put_fd_final() supplies the foreign session&#39;s file table to __ksmbd_close_fd(). The object is then freed without being removed from its owner&#39;s idr, and the owner session later dereferences the stale pointer during file-table teardown. Remove the volatile id from the owner&#39;s idr while ksmbd_close_fd() still holds that table&#39;s lock, and clear volatile_id before dropping the idr-owned reference. A later foreign final put then only performs physical destruction and cannot remove the object from the wrong table.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-74522 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852