33 matches found
CVE-2026-63963
A flaw was found in the Linux kernel's USB Type-C subsystem. A malicious or malformed USB Type-C device could send an invalid Vendor Defined Object VDO count during the Discover Identity Acknowledgement ACK process. This improper validation could allow the device to read beyond the intended memor...
CVE-2026-63963
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers Properly validate the count passed from a device when calling svdmconsumeidentity or svdmconsumeidentitysopprime as the device-controlled value could index of...
CVE-2026-63961
In the Linux kernel, the following vulnerability has been resolved: usb: typec: altmodes/displayport: validate count before reading Status Update VDO A broken/malicious device can send the incorrect count for a status update VDO, which will cause the kernel to read uninitialized stack data and se...
CVE-2026-63963
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers Properly validate the count passed from a device when calling svdmconsumeidentity or svdmconsumeidentitysopprime as the device-controlled value could index of...
CVE-2026-63963
Summary: CVE-2026-63963 affects the Linux kernel USB Type-C TCPM code. Specifically, in Discover Identity ACK handlers, the VDO count passed from a device must be validated before calling svdm_consume_identity() or svdm_consume_identity_sop_prime(). The device-controlled value could index off the...
CVE-2026-63963 usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers Properly validate the count passed from a device when calling svdmconsumeidentity or svdmconsumeidentitysopprime as the device-controlled value could index of...
CVE-2026-63963 usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers
In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpm: validate VDO count in Discover Identity ACK handlers Properly validate the count passed from a device when calling svdmconsumeidentity or svdmconsumeidentitysopprime as the device-controlled value could index of...
CVE-2026-63961 usb: typec: altmodes/displayport: validate count before reading Status Update VDO
In the Linux kernel, the following vulnerability has been resolved: usb: typec: altmodes/displayport: validate count before reading Status Update VDO A broken/malicious device can send the incorrect count for a status update VDO, which will cause the kernel to read uninitialized stack data and se...
PT-2026-61280
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the USB Type-C TCPM TCP Connection Manager component where the count passed from a device is not properly validated when calling the svdm consume identity or svdm...
EUVD-1999-0988
Malware in sbrugna...
vdo bug fix update
An update is available for vdo. This update affects Rocky Linux 8. A Common Vulnerability Scoring System CVSS base score, which gives a detailed severity rating, is available for each vulnerability from the CVE list The vdo packages provide Virtual Data Optimizer VDO, which is a block...
AZL-52749 CVE-2024-50091 affecting package kernel 6.6.126.1-1
In the Linux kernel, the following vulnerability has been resolved: dm vdo: don't refer to dedupecontext after releasing it Clear the dedupecontext pointer in a datavio whenever ownership of the context is lost, so that vdo can't examine it accidentally...
DEBIAN-CVE-2024-50091
In the Linux kernel, the following vulnerability has been resolved: dm vdo: don't refer to dedupecontext after releasing it Clear the dedupecontext pointer in a datavio whenever ownership of the context is lost, so that vdo can't examine it accidentally...
AZL-52616 CVE-2024-50091 affecting package kernel 5.15.200.1-1
In the Linux kernel, the following vulnerability has been resolved: dm vdo: don't refer to dedupecontext after releasing it Clear the dedupecontext pointer in a datavio whenever ownership of the context is lost, so that vdo can't examine it accidentally...
CVE-2024-50091
In the Linux kernel, the following vulnerability has been resolved: dm vdo: don't refer to dedupecontext after releasing it Clear the dedupecontext pointer in a datavio whenever ownership of the context is lost, so that vdo can't examine it accidentally...
CVE-2024-50091 dm vdo: don't refer to dedupe_context after releasing it
In the Linux kernel, the following vulnerability has been resolved: dm vdo: don't refer to dedupecontext after releasing it Clear the dedupecontext pointer in a datavio whenever ownership of the context is lost, so that vdo can't examine it accidentally...
CVE-2024-50091 dm vdo: don't refer to dedupe_context after releasing it
In the Linux kernel, the following vulnerability has been resolved: dm vdo: don't refer to dedupecontext after releasing it Clear the dedupecontext pointer in a datavio whenever ownership of the context is lost, so that vdo can't examine it accidentally...
CVE-2024-50091
Summary: CVE-2024-50091 affects the Linux kernel driver path for dm-vdo, where the code may examine a dedupe_context pointer after ownership is lost. The vulnerability arises from not clearing the dedupe_context pointer in data_vio when ownership changes, enabling a potential misuse if the pointe...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from the dm vdo module failing to clear the pointer to the dedupecontext after releasing it, which could lead to...
PT-2024-33923
Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A vulnerability has been resolved in the Linux kernel related to the dm vdo, where the dedupe context pointer was not cleared in a data vio after releasing it. This could lead to...