
CVE-2022-50060 – octeontx2-af: Fix mcam entry resource leak
https://notcve.org/view.php?id=CVE-2022-50060
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. 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... • https://git.kernel.org/stable/c/c554f9c1574e022821260b24b043a4277e8ec5d8 •

CVE-2022-50059 – ceph: don't leak snap_rwsem in handle_cap_grant
https://notcve.org/view.php?id=CVE-2022-50059
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. 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 r... • https://git.kernel.org/stable/c/6f05b30ea063a2a05dda47a4105a69267ae5270f •

CVE-2022-50058 – vdpa_sim_blk: set number of address spaces and virtqueue groups
https://notcve.org/view.php?id=CVE-2022-50058
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. 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 tw... • https://git.kernel.org/stable/c/bda324fd037a6b0d44da5699574ce741ca161bc4 •

CVE-2022-50057 – fs/ntfs3: Fix NULL deref in ntfs_update_mftmirr
https://notcve.org/view.php?id=CVE-2022-50057
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. • https://git.kernel.org/stable/c/82cae269cfa953032fbb8980a7d554d60fb00b17 •

CVE-2022-50056 – fs/ntfs3: Fix missing i_op in ntfs_read_mft
https://notcve.org/view.php?id=CVE-2022-50056
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. • https://git.kernel.org/stable/c/82cae269cfa953032fbb8980a7d554d60fb00b17 •

CVE-2022-50055 – iavf: Fix adminq error handling
https://notcve.org/view.php?id=CVE-2022-50055
18 Jun 2025 — 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 details: [device address=0x0000000b27ff9000] [size=4096 bytes] [mapped with DMA_BIDIRECTIONAL] [mapped as coherent] 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... • https://git.kernel.org/stable/c/d358aa9a7a2d5f91b1d33d5d4e27c2e46638d123 •

CVE-2022-50054 – iavf: Fix NULL pointer dereference in iavf_get_link_ksettings
https://notcve.org/view.php?id=CVE-2022-50054
18 Jun 2025 — dev_ethtool+0x59/0x170 [ 9385.242848] dev_ethtool+0xa7/0x170 [ 9385.242856] dev_ioctl+0xc3/0x520 [ 9385.242866] sock_do_ioctl+0xa0/0xe0 [ 9385.242877] sock_ioctl+0x22f/0x320 [ 9385.242885] __x64_sys_ioctl+0x84/0xc0 [ 9385.242896] do_syscall_64+0x3a/0x80 [ 9385.242904] entry_SYSCALL_64_after_hwframe+0x46/0xb0 [ 9385.242918] RIP: 0033:0x7f93702396db [ 9385.242923] Code: 73 01 c3 48 8b 0d ad 57 38 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 f... • https://git.kernel.org/stable/c/209f2f9c718138ddbd8586e5a1463bd079a17241 •

CVE-2022-50053 – iavf: Fix reset error handling
https://notcve.org/view.php?id=CVE-2022-50053
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. ... kthread_complete_and_exit+0x20/0x20 [ 5267.217505] ret_from_fork+0x22/0x30 [ 5267.218459] </TASK> 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. • https://git.kernel.org/stable/c/f0db78928783f0a4cce4940e8c03c2e9a760e629 •

CVE-2022-50052 – ASoC: Intel: avs: Fix potential buffer overflow by snprintf()
https://notcve.org/view.php?id=CVE-2022-50052
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). 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 o... • https://git.kernel.org/stable/c/f1b3b320bd6519b16e3480f74f2926d106e3bcba •

CVE-2022-50051 – ASoC: SOF: debug: Fix potential buffer overflow by snprintf()
https://notcve.org/view.php?id=CVE-2022-50051
18 Jun 2025 — In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: debug: 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 the buffer overflow (although it's unrealistic). In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: debug: Fix potential buffer overflow by snprintf() snprintf() returns the would-be-filled size when the string... • https://git.kernel.org/stable/c/5b10b62989219aa527ee4fa555d1995a3b70981b •