Page 273 of 3847 results (0.010 seconds)

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: net: fujitsu: fix potential null-ptr-deref In fmvj18x_get_hwinfo(), if ioremap fails there will be NULL pointer deref. To fix this, check the return value of ioremap and return -1 to the caller in case of failure. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net: fujitsu: corrige el potencial null-ptr-deref En fmvj18x_get_hwinfo(), si ioremap falla, habrá un puntero NULL deref. Para solucionar este problema, verifiqu... • https://git.kernel.org/stable/c/b92170e209f7746ed72eaac98f2c2f4b9af734e6 •

CVSS: 8.4EPSS: 0%CPEs: 2EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: fix a buffer overflow in otx2_set_rxfh_context() This function is called from ethtool_set_rxfh() and "*rss_context" comes from the user. Add some bounds checking to prevent memory corruption. En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: octeontx2-pf: corrige un desbordamiento del búfer en otx2_set_rxfh_context() Esta función se llama desde ethtool_set_rxfh() y "*rss_context" proviene del usuario. Agregu... • https://git.kernel.org/stable/c/81a4362016e7d8b17031fe1aa43cdb58a7f0f163 •

CVSS: 6.2EPSS: 0%CPEs: 2EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: ptp: ocp: Fix a resource leak in an error handling path If an error occurs after a successful 'pci_ioremap_bar()' call, it must be undone by a corresponding 'pci_iounmap()' call, as already done in the remove function. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ptp: ocp: corrige una fuga de recursos en una ruta de manejo de errores. Si se produce un error después de una llamada exitosa a 'pci_ioremap_bar()', se deb... • https://git.kernel.org/stable/c/a7e1abad13f3f0366ee625831fecda2b603cdc17 •

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: mld: fix panic in mld_newpack() mld_newpack() doesn't allow to allocate high order page, only order-0 allocation is allowed. If headroom size is too large, a kernel panic could occur in skb_put(). Test commands: ip netns del A ip netns del B ip netns add A ip netns add B ip link add veth0 type veth peer name veth1 ip link set veth0 netns A ip link set veth1 netns B ip netns exec A ip link set lo up ip... • https://git.kernel.org/stable/c/72e09ad107e78d69ff4d3b97a69f0aad2b77280f •

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: btrfs: do not BUG_ON in link_to_fixup_dir While doing error injection testing I got the following panic kernel BUG at fs/btrfs/tree-log.c:1862! invalid opcode: 0000 [#1] SMP NOPTI CPU: 1 PID: 7836 Comm: mount Not tainted 5.13.0-rc1+ #305 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-2.fc32 04/01/2014 RIP: 0010:link_to_fixup_dir+0xd5/0xe0 RSP: 0018:ffffb5800180fa30 EFLAGS: 00010216 RAX: fffffffffffffffb RBX... • https://git.kernel.org/stable/c/76bfd8ac20bebeae599452a03dfc5724c0475dcf •

CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: drm/amd/amdgpu: fix refcount leak [Why] the gem object rfb->base.obj[0] is get according to num_planes in amdgpufb_create, but is not put according to num_planes [How] put rfb->base.obj[0] in amdgpu_fbdev_destroy according to num_planes En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/amd/amdgpu: corrige la fuga de refcount [Por qué] el objeto gema rfb->base.obj[0] se obtiene según num_planes en amdgpufb_create, ... • https://git.kernel.org/stable/c/599e5d61ace952b0bb9bd942b198bbd0cfded1d7 •

CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: net/smc: remove device from smcd_dev_list after failed device_add() If the device_add() for a smcd_dev fails, there's no cleanup step that rolls back the earlier list_add(). The device subsequently gets freed, and we end up with a corrupted list. Add some error handling that removes the device from the list. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: net/smc: eliminar dispositivo de smcd_dev_list después de fallar de... • https://git.kernel.org/stable/c/c6ba7c9ba43de1b57e9a53946e7ff988554c84ed •

CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix a use-after-free looks like we forget to set ttm->sg to NULL. Hit panic below [ 1235.844104] general protection fault, probably for non-canonical address 0x6b6b6b6b6b6b7b4b: 0000 [#1] SMP DEBUG_PAGEALLOC NOPTI [ 1235.989074] Call Trace: [ 1235.991751] sg_free_table+0x17/0x20 [ 1235.995667] amdgpu_ttm_backend_unbind.cold+0x4d/0xf7 [amdgpu] [ 1236.002288] amdgpu_ttm_backend_destroy+0x29/0x130 [amdgpu] [ 1236.008464] ttm... • https://git.kernel.org/stable/c/0707c3fea8102d211631ba515ef2159707561b0d •

CVSS: 5.5EPSS: 0%CPEs: 4EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: gve: Add NULL pointer checks when freeing irqs. When freeing notification blocks, we index priv->msix_vectors. If we failed to allocate priv->msix_vectors (see abort_with_msix_vectors) this could lead to a NULL pointer dereference if the driver is unloaded. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: gve: agrega comprobaciones de puntero NULL al liberar irqs. Al liberar bloques de notificaciones, indexamos priv->... • https://git.kernel.org/stable/c/893ce44df56580fb878ca5af9c4a5fd87567da50 •

CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0

25 Mar 2024 — In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Clear DMA ops when switching domain Since commit 08a27c1c3ecf ("iommu: Add support to change default domain of an iommu group") a user can switch a device between IOMMU and direct DMA through sysfs. This doesn't work for AMD IOMMU at the moment because dev->dma_ops is not cleared when switching from a DMA to an identity IOMMU domain. The DMA layer thus attempts to use the dma-iommu ops on an identity domain, causing an oops: ... • https://git.kernel.org/stable/c/08a27c1c3ecf5e1da193ce5f8fc97c3be16e75f0 •