CVSS: 5.5EPSS: 0%CPEs: 17EXPL: 0CVE-2024-26920 – tracing/trigger: Fix to return error if failed to alloc snapshot
https://notcve.org/view.php?id=CVE-2024-26920
In the Linux kernel, the following vulnerability has been resolved: tracing/trigger: Fix to return error if failed to alloc snapshot Fix register_snapshot_trigger() to return error code if it failed to allocate a snapshot instead of 0 (success). Unless that, it will register snapshot trigger without an error. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: rastreo/activador: Corrección para devolver error si no se pudo asignar la instantánea. Corrección de Register_snapshot_trigger() para devolver código de error si no se pudo asignar una instantánea en lugar de 0 (éxito). A menos que eso, registrará la activación de la instantánea sin error. • https://git.kernel.org/stable/c/57f2a2ad73e99a7594515848f4da987326a15981 https://git.kernel.org/stable/c/0026e356e51ab3b54322eeb445c75a087ede5b9d https://git.kernel.org/stable/c/0bbe7f719985efd9adb3454679ecef0984cb6800 https://git.kernel.org/stable/c/7c6feb347a4bb1f02e55f6814c93b5f7fab887a8 https://git.kernel.org/stable/c/a289fd864722dcf5363fec66a35965d4964df515 https://git.kernel.org/stable/c/7054f86f268c0d9d62b52a4497dd0e8c10a7e5c7 https://git.kernel.org/stable/c/ffa70d104691aa609a18a9a6692049deb35f431f https://git.kernel.org/stable/c/733c611a758c68894a4480fb999637476 •
CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-26919 – usb: ulpi: Fix debugfs directory leak
https://notcve.org/view.php?id=CVE-2024-26919
In the Linux kernel, the following vulnerability has been resolved: usb: ulpi: Fix debugfs directory leak The ULPI per-device debugfs root is named after the ulpi device's parent, but ulpi_unregister_interface tries to remove a debugfs directory named after the ulpi device itself. This results in the directory sticking around and preventing subsequent (deferred) probes from succeeding. Change the directory name to match the ulpi device. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: usb: ulpi: corrige la fuga del directorio debugfs La raíz debugfs por dispositivo ULPI lleva el nombre del dispositivo principal ulpi, pero ulpi_unregister_interface intenta eliminar un directorio debugfs que lleva el nombre del dispositivo ulpi en sí. Esto da como resultado que el directorio permanezca y evite que las pruebas posteriores (diferidas) se realicen correctamente. • https://git.kernel.org/stable/c/bd0a0a024f2a41e7cc8eadb9862f82c45884b69c https://git.kernel.org/stable/c/d31b886ed6a5095214062ee4fb55037eb930adb6 https://git.kernel.org/stable/c/330d22aba17a4d30a56f007d0f51291d7e00862b https://git.kernel.org/stable/c/33713945cc92ea9c4a1a9479d5c1b7acb7fc4df3 https://git.kernel.org/stable/c/3caf2b2ad7334ef35f55b95f3e1b138c6f77b368 https://access.redhat.com/security/cve/CVE-2024-26919 https://bugzilla.redhat.com/show_bug.cgi?id=2275777 •
CVSS: 6.2EPSS: 0%CPEs: 3EXPL: 0CVE-2024-26918 – PCI: Fix active state requirement in PME polling
https://notcve.org/view.php?id=CVE-2024-26918
In the Linux kernel, the following vulnerability has been resolved: PCI: Fix active state requirement in PME polling The commit noted in fixes added a bogus requirement that runtime PM managed devices need to be in the RPM_ACTIVE state for PME polling. In fact, only devices in low power states should be polled. However there's still a requirement that the device config space must be accessible, which has implications for both the current state of the polled device and the parent bridge, when present. It's not sufficient to assume the bridge remains in D0 and cases have been observed where the bridge passes the D0 test, but the PM state indicates RPM_SUSPENDING and config space of the polled device becomes inaccessible during pci_pme_wakeup(). Therefore, since the bridge is already effectively required to be in the RPM_ACTIVE state, formalize this in the code and elevate the PM usage count to maintain the state while polling the subordinate device. This resolves a regression reported in the bugzilla below where a Thunderbolt/USB4 hierarchy fails to scan for an attached NVMe endpoint downstream of a bridge in a D3hot power state. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: PCI: corrige el requisito de estado activo en el sondeo de PME. La confirmación observada en las correcciones agregó un requisito falso de que los dispositivos administrados por PM en tiempo de ejecución deben estar en el estado RPM_ACTIVE para el sondeo de PME. • https://git.kernel.org/stable/c/d3fcd7360338358aa0036bec6d2cf0e37a0ca624 https://git.kernel.org/stable/c/63b1a3d9dd3b3f6d67f524e76270e66767090583 https://git.kernel.org/stable/c/a4f12e5cbac2865c151d1e97e36eb24205afb23b https://git.kernel.org/stable/c/41044d5360685e78a869d40a168491a70cdb7e73 •
CVSS: -EPSS: 0%CPEs: 11EXPL: 0CVE-2024-26917 – scsi: Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock"
https://notcve.org/view.php?id=CVE-2024-26917
In the Linux kernel, the following vulnerability has been resolved: scsi: Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock" This reverts commit 1a1975551943f681772720f639ff42fbaa746212. This commit causes interrupts to be lost for FCoE devices, since it changed sping locks from "bh" to "irqsave". Instead, a work queue should be used, and will be addressed in a separate commit. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: scsi: Revertir "scsi: fcoe: Reparar posible punto muerto en &fip->ctlr_lock" Esto revierte el commit 1a1975551943f681772720f639ff42fbaa746212. Este commit provoca que se pierdan las interrupciones para los dispositivos FCoE, ya que cambió los bloqueos de sping de "bh" a "irqsave". En su lugar, se debe utilizar una cola de trabajo, que se abordará en un commit separado. • https://git.kernel.org/stable/c/264eae2f523d2aae38188facb4ece893023f25da https://git.kernel.org/stable/c/d2bf25674cea74b865d367d09be5dfe9aff5922a https://git.kernel.org/stable/c/9cce8ef7a6fa858bbcacd8679a5ca5a4fd3a6df3 https://git.kernel.org/stable/c/076fb40cf27ab9232d8cce1f007e663e46705302 https://git.kernel.org/stable/c/5a5fb3b1754fa2b4db95f0151b4af0fb6f8918ec https://git.kernel.org/stable/c/1a1975551943f681772720f639ff42fbaa746212 https://git.kernel.org/stable/c/4ea46b479a00dd232f0dbc81fdc27f9330ecb3ad https://git.kernel.org/stable/c/694ddc5bf35a5b6f9acb6e4724324c910 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-26916 – Revert "drm/amd: flush any delayed gfxoff on suspend entry"
https://notcve.org/view.php?id=CVE-2024-26916
In the Linux kernel, the following vulnerability has been resolved: Revert "drm/amd: flush any delayed gfxoff on suspend entry" commit ab4750332dbe ("drm/amdgpu/sdma5.2: add begin/end_use ring callbacks") caused GFXOFF control to be used more heavily and the codepath that was removed from commit 0dee72639533 ("drm/amd: flush any delayed gfxoff on suspend entry") now can be exercised at suspend again. Users report that by using GNOME to suspend the lockscreen trigger will cause SDMA traffic and the system can deadlock. This reverts commit 0dee726395333fea833eaaf838bc80962df886c8. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: Revertir "drm/amd: eliminar cualquier gfxoff retrasado al suspender la entrada" commit ab4750332dbe ("drm/amdgpu/sdma5.2: agregar devoluciones de llamada de anillo de inicio/fin de uso") provocó que el control de GFXOFF se utilizará más intensamente y la ruta de código que se eliminó del commit 0dee72639533 ("drm/amd: eliminar cualquier gfxoff retrasado al suspender la entrada") ahora se puede ejercer nuevamente en suspensión. Los usuarios informan que al usar GNOME para suspender el activador de la pantalla de bloqueo provocará tráfico SDMA y el sistema puede bloquearse. Esto revierte el commit 0dee726395333fea833eaaf838bc80962df886c8. • https://git.kernel.org/stable/c/f94942885e8416ce9de84d8fae93684002682b5d https://git.kernel.org/stable/c/78b2ba39beef21c8baebb1868569c2026ad76de0 https://git.kernel.org/stable/c/3aae4ef4d799fb3d0381157640fdb251008cf0ae https://git.kernel.org/stable/c/ab4750332dbe535243def5dcebc24ca00c1f98ac https://git.kernel.org/stable/c/65158edb0a3a8df23197d52cd24287e39eaf95d6 https://git.kernel.org/stable/c/ff70e6ff6fc2413caf33410af7462d1f584d927e https://git.kernel.org/stable/c/caa2565a2e13899be31f7b1e069e6465d3e2adb0 https://git.kernel.org/stable/c/d855ceb6a5fde668c5431156bc60fae0c •