Количество 49
Количество 49

CVE-2024-53214
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capability...

CVE-2024-53214
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capability...

CVE-2024-53214
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capabili
CVE-2024-53214
In the Linux kernel, the following vulnerability has been resolved: v ...
GHSA-4rwh-4cv9-9p66
In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capab...

BDU:2025-04322
Уязвимость компонентов vfio/pci ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании

SUSE-SU-2025:02507-1
Security update for the Linux Kernel (Live Patch 60 for SLE 12 SP5)

SUSE-SU-2025:02415-1
Security update for the Linux Kernel (Live Patch 63 for SLE 12 SP5)

SUSE-SU-2025:02396-1
Security update for the Linux Kernel (Live Patch 61 for SLE 12 SP5)

SUSE-SU-2025:02454-1
Security update for the Linux Kernel (Live Patch 51 for SLE 15 SP3)

SUSE-SU-2025:02422-1
Security update for the Linux Kernel (Live Patch 57 for SLE 12 SP5)

SUSE-SU-2025:02392-1
Security update for the Linux Kernel (Live Patch 59 for SLE 12 SP5)

SUSE-SU-2025:02391-1
Security update for the Linux Kernel (Live Patch 58 for SLE 12 SP5)

SUSE-SU-2025:02446-1
Security update for the Linux Kernel (Live Patch 49 for SLE 15 SP3)

SUSE-SU-2025:02428-1
Security update for the Linux Kernel (Live Patch 48 for SLE 15 SP3)

SUSE-SU-2025:02410-1
Security update for the Linux Kernel (Live Patch 21 for SLE 15 SP5)

SUSE-SU-2025:02401-1
Security update for the Linux Kernel (Live Patch 33 for SLE 15 SP4)

SUSE-SU-2025:02459-1
Security update for the Linux Kernel (Live Patch 17 for SLE 15 SP5)

SUSE-SU-2025:02434-1
Security update for the Linux Kernel (Live Patch 31 for SLE 15 SP4)

SUSE-SU-2025:02433-1
Security update for the Linux Kernel (Live Patch 6 for SLE 15 SP6)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
---|---|---|---|---|
![]() | CVE-2024-53214 In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capability... | 0% Низкий | 7 месяцев назад | |
![]() | CVE-2024-53214 In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capability... | CVSS3: 5.5 | 0% Низкий | 7 месяцев назад |
![]() | CVE-2024-53214 In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capabili | 0% Низкий | 7 месяцев назад | |
CVE-2024-53214 In the Linux kernel, the following vulnerability has been resolved: v ... | 0% Низкий | 7 месяцев назад | ||
GHSA-4rwh-4cv9-9p66 In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID greater than PCI_EXT_CAP_ID_MAX) or a capability that is intentionally chosen to be hidden from the user. Hiding a capability is done by virtualizing and modifying the 'Next Capability Offset' field of the previous capability so it points to the capability after the one that should be hidden. The special case where the first capability in the list should be hidden is handled differently because there is no previous capability that can be modified. In this case, the capability ID and version are zeroed while leaving the next pointer intact. This hides the capability and leaves an anchor for the rest of the capability list. However, today, hiding the first capability in the list is not done properly if the capab... | 0% Низкий | 7 месяцев назад | ||
![]() | BDU:2025-04322 Уязвимость компонентов vfio/pci ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 7.8 | 0% Низкий | 7 месяцев назад |
![]() | SUSE-SU-2025:02507-1 Security update for the Linux Kernel (Live Patch 60 for SLE 12 SP5) | 12 дней назад | ||
![]() | SUSE-SU-2025:02415-1 Security update for the Linux Kernel (Live Patch 63 for SLE 12 SP5) | 14 дней назад | ||
![]() | SUSE-SU-2025:02396-1 Security update for the Linux Kernel (Live Patch 61 for SLE 12 SP5) | 15 дней назад | ||
![]() | SUSE-SU-2025:02454-1 Security update for the Linux Kernel (Live Patch 51 for SLE 15 SP3) | 14 дней назад | ||
![]() | SUSE-SU-2025:02422-1 Security update for the Linux Kernel (Live Patch 57 for SLE 12 SP5) | 14 дней назад | ||
![]() | SUSE-SU-2025:02392-1 Security update for the Linux Kernel (Live Patch 59 for SLE 12 SP5) | 16 дней назад | ||
![]() | SUSE-SU-2025:02391-1 Security update for the Linux Kernel (Live Patch 58 for SLE 12 SP5) | 16 дней назад | ||
![]() | SUSE-SU-2025:02446-1 Security update for the Linux Kernel (Live Patch 49 for SLE 15 SP3) | 14 дней назад | ||
![]() | SUSE-SU-2025:02428-1 Security update for the Linux Kernel (Live Patch 48 for SLE 15 SP3) | 14 дней назад | ||
![]() | SUSE-SU-2025:02410-1 Security update for the Linux Kernel (Live Patch 21 for SLE 15 SP5) | 15 дней назад | ||
![]() | SUSE-SU-2025:02401-1 Security update for the Linux Kernel (Live Patch 33 for SLE 15 SP4) | 15 дней назад | ||
![]() | SUSE-SU-2025:02459-1 Security update for the Linux Kernel (Live Patch 17 for SLE 15 SP5) | 14 дней назад | ||
![]() | SUSE-SU-2025:02434-1 Security update for the Linux Kernel (Live Patch 31 for SLE 15 SP4) | 14 дней назад | ||
![]() | SUSE-SU-2025:02433-1 Security update for the Linux Kernel (Live Patch 6 for SLE 15 SP6) | 14 дней назад |
Уязвимостей на страницу