https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 07:35:11 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-07755 bdu:2024-07755 https://cve.radiocsirt.org/vuln/bdu:2024-07755 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0693 certfr-2024-avi-0693 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0693 https://cve.radiocsirt.org/vuln/euvd-2026-344587 EUVD-2026-344587 https://cve.radiocsirt.org/vuln/euvd-2026-344587 https://cve.radiocsirt.org/vuln/fkie_cve-2022-48792 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task</p> <p>Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_completion() or mpi_sata_completion().</p> <p>In this case, the following are the two steps in handling those I/O completions:</p> <p>- Call complete() to inform the upper layer handler of completion of the I/O.</p> <p>- Release driver resources associated with the sas_task in pm8001_ccb_task_free() call.</p> <p>When complete() is called, the upper layer may free the sas_task. As such, we should not touch the associated sas_task afterwards, but we do so in the pm8001_ccb_task_free() call.</p> <p>Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task</p> <p>Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_completion() or mpi_sata_completion().</p> <p>In this case, the following are the two steps in handling those I/O completions:</p> <p>- Call complete() to inform the upper layer handler of completion of the I/O.</p> <p>- Release driver resources associated with the sas_task in pm8001_ccb_task_free() call.</p> <p>When complete() is called, the upper layer may free the sas_task. As such, we should not touch the associated sas_task afterwards, but we do so in the pm8001_ccb_task_free() call.</p> <p>Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2022-48792 https://cve.radiocsirt.org/vuln/ghsa-x9wp-3948-xg4x <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task</p> <p>Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_completion() or mpi_sata_completion().</p> <p>In this case, the following are the two steps in handling those I/O completions:</p> <p>- Call complete() to inform the upper layer handler of completion of the I/O.</p> <p>- Release driver resources associated with the sas_task in pm8001_ccb_task_free() call.</p> <p>When complete() is called, the upper layer may free the sas_task. As such, we should not touch the associated sas_task afterwards, but we do so in the pm8001_ccb_task_free() call.</p> <p>Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task</p> <p>Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_completion() or mpi_sata_completion().</p> <p>In this case, the following are the two steps in handling those I/O completions:</p> <p>- Call complete() to inform the upper layer handler of completion of the I/O.</p> <p>- Release driver resources associated with the sas_task in pm8001_ccb_task_free() call.</p> <p>When complete() is called, the upper layer may free the sas_task. As such, we should not touch the associated sas_task afterwards, but we do so in the pm8001_ccb_task_free() call.</p> <p>Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.</p> https://cve.radiocsirt.org/vuln/ghsa-x9wp-3948-xg4x https://cve.radiocsirt.org/vuln/suse-su-2024:2892-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:2892-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48792 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 108 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_completion() or mpi_sata_completion(). In this case, the following are the two steps in handling those I/O completions: - Call complete() to inform the upper layer handler of completion of the I/O. - Release driver resources associated with the sas_task in pm8001_ccb_task_free() call. When complete() is called, the upper layer may free the sas_task. As such, we should not touch the associated sas_task afterwards, but we do so in the pm8001_ccb_task_free() call. Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 108 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix use-after-free for aborted SSP/STP sas_task Currently a use-after-free may occur if a sas_task is aborted by the upper layer before we handle the I/O completion in mpi_ssp_completion() or mpi_sata_completion(). In this case, the following are the two steps in handling those I/O completions: - Call complete() to inform the upper layer handler of completion of the I/O. - Release driver resources associated with the sas_task in pm8001_ccb_task_free() call. When complete() is called, the upper layer may free the sas_task. As such, we should not touch the associated sas_task afterwards, but we do so in the pm8001_ccb_task_free() call. Fix by swapping the complete() and pm8001_ccb_task_free() calls ordering.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-48792 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1625