CVE-2025-40343 nvmet-fc: avoid scheduling association deletion twice

In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid scheduling association deletion twice When forcefully shutting down a port via the configfs interface, nvmetportsubsysdroplink first calls nvmetportdelctrls and then nvmetdisableport. Both functions will eventuall...

CVE-2025-40343

CVE-2025-40343 affects the Linux kernel nvmet-fc component. When forcefully shutting down a port via configfs, nvmet_port_subsys_drop_link() calls nvmet_port_del_ctrls() and then nvmet_disable_port(), which both schedule deletion of remaining associations. The bug allows the first scheduled work ...

CVE-2025-40343 nvmet-fc: avoid scheduling association deletion twice

In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid scheduling association deletion twice When forcefully shutting down a port via the configfs interface, nvmetportsubsysdroplink first calls nvmetportdelctrls and then nvmetdisableport. Both functions will eventuall...

CVE-2025-40342 nvme-fc: use lock accessing port_state and rport state

In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing portstate and rport state nvmefcunregisterremote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reconnect logic, because...

CVE-2025-40342

In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing portstate and rport state nvmefcunregisterremote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reconnect logic, because...

CVE-2025-40342

In CVE-2025-40342, a race condition in the Linux kernel NVMe host/fc driver arises when nvme_fc_unregister_remote can remove a remote port while there is no active association, because nvme_fc_create_association does not atomically check port_state and increment the rport active count without pro...

CVE-2025-40342 nvme-fc: use lock accessing port_state and rport state

In the Linux kernel, the following vulnerability has been resolved: nvme-fc: use lock accessing portstate and rport state nvmefcunregisterremote removes the remote port on a lport object at any point in time when there is no active association. This races with with the reconnect logic, because...

EUVD-2022-55709

In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as insb', outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested...

CVE-2023-53851 drm/msm/dp: Drop aux devices together with DP controller

In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: Drop aux devices together with DP controller Using devres to depopulate the aux bus made sure that upon a probe deferral the EDP panel device would be destroyed and recreated upon next attempt. But the struct device...

CVE-2023-53851 drm/msm/dp: Drop aux devices together with DP controller

In the Linux kernel, the following vulnerability has been resolved: drm/msm/dp: Drop aux devices together with DP controller Using devres to depopulate the aux bus made sure that upon a probe deferral the EDP panel device would be destroyed and recreated upon next attempt. But the struct device...

CVE-2023-53841 devlink: report devlink_port_type_warn source device

In the Linux kernel, the following vulnerability has been resolved: devlink: report devlinkporttypewarn source device devlinkporttypewarn is scheduled for port devlink and warning when the port type is not set. But from this warning it is not easy found out which device driver has no devlink port...

CVE-2023-53841

In the Linux kernel, the following vulnerability has been resolved: devlink: report devlinkporttypewarn source device devlinkporttypewarn is scheduled for port devlink and warning when the port type is not set. But from this warning it is not easy found out which device driver has no devlink port...

CVE-2023-53841 devlink: report devlink_port_type_warn source device

In the Linux kernel, the following vulnerability has been resolved: devlink: report devlinkporttypewarn source device devlinkporttypewarn is scheduled for port devlink and warning when the port type is not set. But from this warning it is not easy found out which device driver has no devlink port...

CVE-2023-53841

The CVE-2023-53841 issue in the Linux kernel was resolved by a patch that prevents or clarifies the devlink_port_type_warn warning when a devlink port type is not set. The vulnerability manifested as a warning "Type was not set for devlink port" from devlink_port_type_warn in net/devlink/leftover...

CVE-2022-50647

In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as insb', outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested...

DEBIAN-CVE-2022-50647

In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as insb', outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested...

UBUNTU-CVE-2022-50647

In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as insb', outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested...

SUSE CVE-2025-40297

In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix use-after-free due to MST port state bypass syzbot reported1 a use-after-free when deleting an expired fdb. It is due to a race condition between learning still happening and a port being deleted, after all its...

CVE-2022-50647

CVE-2022-50647 relates to a Linux kernel issue on RISC‑V where port I/O string accessors (insb/outsb, etc.) used the physical PCI port I/O address instead of memory mapping, breaking parport/PCIe parallel-port accesses and causing kernel faults (memory access fault: Unable to handle kernel access...

CVE-2022-50647 RISC-V: Make port I/O string accessors actually work

In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as insb', outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested...