Page 18 of 5911 results (0.023 seconds)

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak." In the Linux kernel, the following vulnerability has been resolved: pinctrl: nomadik: Fix refcount leak in nmk_pinctrl_dt_subnode_to_map of_parse_phandle() returns a node pointer with refcount incre... • https://git.kernel.org/stable/c/c2f6d059abfc29822af732e4da70813a5b6fd9cd •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: Fix mcam entry resource leak The teardown sequence in FLR handler returns if no NIX LF is attached to PF/VF because it indicates that graceful shutdown of resources already happened. But there is a chance of all allocated MCAM entries not being freed by PF/VF. Hence free mcam entries even in case of detached LF. In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: Fix mcam entry resource leak The t... • https://git.kernel.org/stable/c/c554f9c1574e022821260b24b043a4277e8ec5d8 •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ceph: don't leak snap_rwsem in handle_cap_grant When handle_cap_grant is called on an IMPORT op, then the snap_rwsem is held and the function is expected to release it before returning. It currently fails to do that in all cases which could lead to a deadlock. In the Linux kernel, the following vulnerability has been resolved: ceph: don't leak snap_rwsem in handle_cap_grant When handle_cap_grant is called on an IMPORT op, then the snap_rwse... • https://git.kernel.org/stable/c/6f05b30ea063a2a05dda47a4105a69267ae5270f •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: vdpa_sim_blk: set number of address spaces and virtqueue groups Commit bda324fd037a ("vdpasim: control virtqueue support") added two new fields (nas, ngroups) to vdpasim_dev_attr, but we forgot to initialize them for vdpa_sim_blk. When creating a new vdpa_sim_blk device this causes the kernel to panic in this way: $ vdpa dev add mgmtdev vdpasim_blk name blk0 BUG: kernel NULL pointer dereference, address: 0000000000000030 ... RIP: 0010:vhost... • https://git.kernel.org/stable/c/bda324fd037a6b0d44da5699574ce741ca161bc4 •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix NULL deref in ntfs_update_mftmirr If ntfs_fill_super() wasn't called then sbi->sb will be equal to NULL. Code should check this ptr before dereferencing. Syzbot hit this issue via passing wrong mount param as can be seen from log below Fail log: ntfs3: Unknown parameter 'iochvrset' general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000... • https://git.kernel.org/stable/c/82cae269cfa953032fbb8980a7d554d60fb00b17 •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix missing i_op in ntfs_read_mft There is null pointer dereference because i_op == NULL. The bug happens because we don't initialize i_op for records in $Extend. In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix missing i_op in ntfs_read_mft There is null pointer dereference because i_op == NULL. The bug happens because we don't initialize i_op for records in $Extend. • https://git.kernel.org/stable/c/82cae269cfa953032fbb8980a7d554d60fb00b17 •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: iavf: Fix adminq error handling iavf_alloc_asq_bufs/iavf_alloc_arq_bufs allocates with dma_alloc_coherent memory for VF mailbox. Free DMA regions for both ASQ and ARQ in case error happens during configuration of ASQ/ARQ registers. Without this change it is possible to see when unloading interface: 74626.583369: dma_debug_device_change: device driver has pending DMA allocations while released from device [count=32] One of leaked entries det... • https://git.kernel.org/stable/c/d358aa9a7a2d5f91b1d33d5d4e27c2e46638d123 •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: iavf: Fix NULL pointer dereference in iavf_get_link_ksettings Fix possible NULL pointer dereference, due to freeing of adapter->vf_res in iavf_init_get_resources. Previous commit introduced a regression, where receiving IAVF_ERR_ADMIN_QUEUE_NO_WORK from iavf_get_vf_config would free adapter->vf_res. However, netdev is still registered, so ethtool_ops can be called. Calling iavf_get_link_ksettings with no vf_res, will result with: [ 9385.242... • https://git.kernel.org/stable/c/209f2f9c718138ddbd8586e5a1463bd079a17241 •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: iavf: Fix reset error handling Do not call iavf_close in iavf_reset_task error handling. Doing so can lead to double call of napi_disable, which can lead to deadlock there. Removing VF would lead to iavf_remove task being stuck, because it requires crit_lock, which is held by iavf_close. Call iavf_disable_vf if reset fail, so that driver will clean up remaining invalid resources. During rapid VF resets, HW can fail to setup VF mailbox. Wron... • https://git.kernel.org/stable/c/f0db78928783f0a4cce4940e8c03c2e9a760e629 •

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

18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: avs: Fix potential buffer overflow by snprintf() snprintf() returns the would-be-filled size when the string overflows the given buffer size, hence using this value may result in a buffer overflow (although it's unrealistic). This patch replaces it with a safer version, scnprintf() for papering over such a potential issue. In the Linux kernel, the following vulnerability has been resolved: ASoC: Intel: avs: Fix potential buffer... • https://git.kernel.org/stable/c/f1b3b320bd6519b16e3480f74f2926d106e3bcba •