CVE-2023-52871

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: llcc: Handle a second device without data corruption Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drvdata pointer. So check if drvdata is valid...

CVE-2023-52765

In the Linux kernel, the following vulnerability has been resolved: mfd: qcom-spmi-pmic: Fix revid implementation The Qualcomm SPMI PMIC revid implementation is broken in multiple ways. First, it assumes that just because the sibling base device has been registered that means that it is also boun...

CVE-2023-52871 soc: qcom: llcc: Handle a second device without data corruption

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: llcc: Handle a second device without data corruption Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drvdata pointer. So check if drvdata is valid...

CVE-2023-52871 soc: qcom: llcc: Handle a second device without data corruption

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: llcc: Handle a second device without data corruption Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drvdata pointer. So check if drvdata is valid...

CVE-2023-52871

CVE-2023-52871 relates to a Linux kernel flaw in soc: qcom: llcc where a second device could lead to data corruption because a failed probe might overwrite the global drv_data pointer. The fix is to validate drv_data before overwriting it. Public notices (NVD entry and Nessus advisories) reiterat...

CVE-2023-52871

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: llcc: Handle a second device without data corruption Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drvdata pointer. So check if drvdata is valid...

CVE-2023-52765 mfd: qcom-spmi-pmic: Fix revid implementation

In the Linux kernel, the following vulnerability has been resolved: mfd: qcom-spmi-pmic: Fix revid implementation The Qualcomm SPMI PMIC revid implementation is broken in multiple ways. First, it assumes that just because the sibling base device has been registered that means that it is also boun...

CVE-2023-52765 mfd: qcom-spmi-pmic: Fix revid implementation

In the Linux kernel, the following vulnerability has been resolved: mfd: qcom-spmi-pmic: Fix revid implementation The Qualcomm SPMI PMIC revid implementation is broken in multiple ways. First, it assumes that just because the sibling base device has been registered that means that it is also boun...

CVE-2021-47311

In the Linux kernel, the following vulnerability has been resolved: net: qcom/emac: fix UAF in emacremove adpt is netdev private data and it cannot be used after freenetdev call. Using adpt after freenetdev can cause UAF bug. Fix it by moving freenetdev at the end of the function...

CVE-2021-47311

In the Linux kernel, the following vulnerability has been resolved: net: qcom/emac: fix UAF in emacremove adpt is netdev private data and it cannot be used after freenetdev call. Using adpt after freenetdev can cause UAF bug. Fix it by moving freenetdev at the end of the function...

DEBIAN-CVE-2021-47311

In the Linux kernel, the following vulnerability has been resolved: net: qcom/emac: fix UAF in emacremove adpt is netdev private data and it cannot be used after freenetdev call. Using adpt after freenetdev can cause UAF bug. Fix it by moving freenetdev at the end of the function...

CVE-2021-47311

In the Linux kernel, the following vulnerability has been resolved: net: qcom/emac: fix UAF in emacremove adpt is netdev private data and it cannot be used after freenetdev call. Using adpt after freenetdev can cause UAF bug. Fix it by moving freenetdev at the end of the function...

UBUNTU-CVE-2021-47311

In the Linux kernel, the following vulnerability has been resolved: net: qcom/emac: fix UAF in emacremove adpt is netdev private data and it cannot be used after freenetdev call. Using adpt after freenetdev can cause UAF bug. Fix it by moving freenetdev at the end of the function...

CVE-2021-47311 net: qcom/emac: fix UAF in emac_remove

In the Linux kernel, the following vulnerability has been resolved: net: qcom/emac: fix UAF in emacremove adpt is netdev private data and it cannot be used after freenetdev call. Using adpt after freenetdev can cause UAF bug. Fix it by moving freenetdev at the end of the function...

CVE-2021-47311

CVE-2021-47311 is a Linux kernel memory use-after-free (UAF) vulnerability in net: qcom/emac, caused by private data (adpt) being used after free_netdev() is called. The fix moves free_netdev() to the end of emac_remove to ensure adpt is not accessed after the netdev is freed. Public advisories (...

CVE-2021-47311 net: qcom/emac: fix UAF in emac_remove

In the Linux kernel, the following vulnerability has been resolved: net: qcom/emac: fix UAF in emacremove adpt is netdev private data and it cannot be used after freenetdev call. Using adpt after freenetdev can cause UAF bug. Fix it by moving freenetdev at the end of the function...

CVE-2024-35994

A vulnerability was found in the Qualcomm firmware driver qcomqseecomuefisecapp in the Linux kernel. It arises from incorrect memory allocation for request and response buffers in the QSEECOM APPSEND command. The driver expects both buffers to be in a single memory region, but they are allocated...

CVE-2024-35994

In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: uefisecapp: Fix memory related IO errors and crashes It turns out that while the QSEECOM APPSEND command has specific fields for request and response buffers, uefisecapp expects them both to be in a single memory...

CVE-2024-35994

In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: uefisecapp: Fix memory related IO errors and crashes It turns out that while the QSEECOM APPSEND command has specific fields for request and response buffers, uefisecapp expects them both to be in a single memory...

UBUNTU-CVE-2024-35994

In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: uefisecapp: Fix memory related IO errors and crashes It turns out that while the QSEECOM APPSEND command has specific fields for request and response buffers, uefisecapp expects them both to be in a single memory...