linux package
kernel
pkg:linux/kernel
Vulnerabilities (1,755)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-53742 | — | >= 5.8.0, < 6.1.28 | 6.1.28 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: kcsan: Avoid READ_ONCE() in read_instrumented_memory() Haibo Li reported: | Unable to handle kernel paging request at virtual address | ffffff802a0d8d7171 | Mem abort info:o: | ESR = 0x9600002121 | | ||
| CVE-2022-50630 | — | >= 4.11.0, < 5.10.150 | 5.10.150 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: fix UAF in hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and reacquire them again after handle_userfault(), but reacquire the vma_lock could le | ||
| CVE-2022-50629 | — | >= 4.17.0, < 4.19.276 | 4.19.276 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: Fix memory leak in rsi_coex_attach() The coex_cb needs to be freed when rsi_create_kthread() failed in rsi_coex_attach(). | ||
| CVE-2022-50628 | — | >= 5.13.0, < 6.1.16 | 6.1.16 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/gud: Fix UBSAN warning UBSAN complains about invalid value for bool: [ 101.165172] [drm] Initialized gud 1.0.0 20200422 for 2-3.2:1.0 on minor 1 [ 101.213360] gud 2-3.2:1.0: [drm] fb1: guddrmfb frame buf | ||
| CVE-2022-50627 | — | >= 5.6.0, < 6.1.16 | 6.1.16 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix monitor mode bringup crash When the interface is brought up in monitor mode, it leads to NULL pointer dereference crash. This crash happens when the packet type is extracted for a SKB. This ex | ||
| CVE-2022-50626 | — | >= 2.6.19, < 4.9.337 | 4.9.337 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: fix memory leak in dvb_usb_adapter_init() Syzbot reports a memory leak in "dvb_usb_adapter_init()". The leak is due to not accounting for and freeing current iteration's adapter->priv in case of | ||
| CVE-2022-50625 | — | >= 4.2.0, < 4.9.337 | 4.9.337 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: serial: amba-pl011: avoid SBSA UART accessing DMACR register Chapter "B Generic UART" in "ARM Server Base System Architecture" [1] documentation describes a generic UART interface. Such generic UART does not su | ||
| CVE-2022-50624 | — | >= 4.16.0, < 4.19.264 | 4.19.264 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: net: netsec: fix error handling in netsec_register_mdio() If phy_device_register() fails, phy_device_free() need be called to put refcount, so memory of phy device and device name can be freed in callback funct | ||
| CVE-2022-50623 | — | >= 5.9.0, < 5.10.150 | 5.10.150 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: fpga: prevent integer overflow in dfl_feature_ioctl_set_irq() The "hdr.count * sizeof(s32)" multiplication can overflow on 32 bit systems leading to memory corruption. Use array_size() to fix that. | ||
| CVE-2022-50622 | — | >= 5.10.0, < 5.10.150 | 5.10.150 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential memory leak in ext4_fc_record_modified_inode() As krealloc may return NULL, in this case 'state->fc_modified_inodes' may not be freed by krealloc, but 'state->fc_modified_inodes' already set | ||
| CVE-2022-50621 | — | >= 6.0.0, < 6.0.3 | 6.0.3 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: dm: verity-loadpin: Only trust verity targets with enforcement Verity targets can be configured to ignore corrupted data blocks. LoadPin must only trust verity targets that are configured to perform some kind o | ||
| CVE-2022-50620 | — | >= 5.15.0, < 5.15.86 | 5.15.86 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to invalidate dcc->f2fs_issue_discard in error path Syzbot reports a NULL pointer dereference issue as below: __refcount_add include/linux/refcount.h:193 [inline] __refcount_inc include/linux/refco | ||
| CVE-2022-50619 | — | >= 5.14.0, < 5.15.77 | 5.15.77 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix memory leak in kfd_mem_dmamap_userptr() If the number of pages from the userptr BO differs from the SG BO then the allocated memory for the SG table doesn't get freed before returning -EINVAL, w | ||
| CVE-2022-50618 | — | >= 4.10.0, < 4.19.270 | 4.19.270 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: mmc: meson-gx: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, it will lead two issues: 1. The memory that allocated in mmc_alloc_host() is leaked. 2. In | ||
| CVE-2022-50617 | — | >= 5.11.0, < 5.15.86 | 5.15.86 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/powerplay/psm: Fix memory leak in power state init Commit 902bc65de0b3 ("drm/amdgpu/powerplay/psm: return an error in power state init") made the power state init function return early in case of fai | ||
| CVE-2022-50616 | — | >= 3.18.0, < 6.0.16 | 6.0.16 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: regulator: core: Use different devices for resource allocation and DT lookup Following by the below discussion, there's the potential UAF issue between regulator and mfd. https://lore.kernel.org/all/20221128143 | ||
| CVE-2022-50615 | — | >= 5.3.0, < 5.10.163 | 5.10.163 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix reference count leak in snr_uncore_mmio_map() pci_get_device() will increase the reference count for the returned pci_dev, so snr_uncore_get_mc_dev() will return a pci_dev with its re | ||
| CVE-2022-50614 | — | >= 4.15.0, < 5.10.148 | 5.10.148 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic The dma_map_single() doesn't permit zero length mapping. It causes a follow panic. A panic was reported on arm64: [ 60.137988] ------ | ||
| CVE-2022-50583 | — | >= 5.19.0, < 6.0.16 | 6.0.16 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: md/raid0, raid10: Don't set discard sectors for request queue It should use disk_stack_limits to get a proper max_discard_sectors rather than setting a value by stack drivers. And there is a bug. If all member | ||
| CVE-2025-40326 | — | >= 6.14.0, < 6.17.8 | 6.17.8 | Dec 8, 2025 | In the Linux kernel, the following vulnerability has been resolved: NFSD: Define actions for the new time_deleg FATTR4 attributes NFSv4 clients won't send legitimate GETATTR requests for these new attributes because they are intended to be used only with CB_GETATTR and SETATTR. |
- CVE-2023-53742Dec 8, 2025affected >= 5.8.0, < 6.1.28fixed 6.1.28
In the Linux kernel, the following vulnerability has been resolved: kcsan: Avoid READ_ONCE() in read_instrumented_memory() Haibo Li reported: | Unable to handle kernel paging request at virtual address | ffffff802a0d8d7171 | Mem abort info:o: | ESR = 0x9600002121 |
- CVE-2022-50630Dec 8, 2025affected >= 4.11.0, < 5.10.150fixed 5.10.150
In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: fix UAF in hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and reacquire them again after handle_userfault(), but reacquire the vma_lock could le
- CVE-2022-50629Dec 8, 2025affected >= 4.17.0, < 4.19.276fixed 4.19.276
In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: Fix memory leak in rsi_coex_attach() The coex_cb needs to be freed when rsi_create_kthread() failed in rsi_coex_attach().
- CVE-2022-50628Dec 8, 2025affected >= 5.13.0, < 6.1.16fixed 6.1.16
In the Linux kernel, the following vulnerability has been resolved: drm/gud: Fix UBSAN warning UBSAN complains about invalid value for bool: [ 101.165172] [drm] Initialized gud 1.0.0 20200422 for 2-3.2:1.0 on minor 1 [ 101.213360] gud 2-3.2:1.0: [drm] fb1: guddrmfb frame buf
- CVE-2022-50627Dec 8, 2025affected >= 5.6.0, < 6.1.16fixed 6.1.16
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix monitor mode bringup crash When the interface is brought up in monitor mode, it leads to NULL pointer dereference crash. This crash happens when the packet type is extracted for a SKB. This ex
- CVE-2022-50626Dec 8, 2025affected >= 2.6.19, < 4.9.337fixed 4.9.337
In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: fix memory leak in dvb_usb_adapter_init() Syzbot reports a memory leak in "dvb_usb_adapter_init()". The leak is due to not accounting for and freeing current iteration's adapter->priv in case of
- CVE-2022-50625Dec 8, 2025affected >= 4.2.0, < 4.9.337fixed 4.9.337
In the Linux kernel, the following vulnerability has been resolved: serial: amba-pl011: avoid SBSA UART accessing DMACR register Chapter "B Generic UART" in "ARM Server Base System Architecture" [1] documentation describes a generic UART interface. Such generic UART does not su
- CVE-2022-50624Dec 8, 2025affected >= 4.16.0, < 4.19.264fixed 4.19.264
In the Linux kernel, the following vulnerability has been resolved: net: netsec: fix error handling in netsec_register_mdio() If phy_device_register() fails, phy_device_free() need be called to put refcount, so memory of phy device and device name can be freed in callback funct
- CVE-2022-50623Dec 8, 2025affected >= 5.9.0, < 5.10.150fixed 5.10.150
In the Linux kernel, the following vulnerability has been resolved: fpga: prevent integer overflow in dfl_feature_ioctl_set_irq() The "hdr.count * sizeof(s32)" multiplication can overflow on 32 bit systems leading to memory corruption. Use array_size() to fix that.
- CVE-2022-50622Dec 8, 2025affected >= 5.10.0, < 5.10.150fixed 5.10.150
In the Linux kernel, the following vulnerability has been resolved: ext4: fix potential memory leak in ext4_fc_record_modified_inode() As krealloc may return NULL, in this case 'state->fc_modified_inodes' may not be freed by krealloc, but 'state->fc_modified_inodes' already set
- CVE-2022-50621Dec 8, 2025affected >= 6.0.0, < 6.0.3fixed 6.0.3
In the Linux kernel, the following vulnerability has been resolved: dm: verity-loadpin: Only trust verity targets with enforcement Verity targets can be configured to ignore corrupted data blocks. LoadPin must only trust verity targets that are configured to perform some kind o
- CVE-2022-50620Dec 8, 2025affected >= 5.15.0, < 5.15.86fixed 5.15.86
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to invalidate dcc->f2fs_issue_discard in error path Syzbot reports a NULL pointer dereference issue as below: __refcount_add include/linux/refcount.h:193 [inline] __refcount_inc include/linux/refco
- CVE-2022-50619Dec 8, 2025affected >= 5.14.0, < 5.15.77fixed 5.15.77
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix memory leak in kfd_mem_dmamap_userptr() If the number of pages from the userptr BO differs from the SG BO then the allocated memory for the SG table doesn't get freed before returning -EINVAL, w
- CVE-2022-50618Dec 8, 2025affected >= 4.10.0, < 4.19.270fixed 4.19.270
In the Linux kernel, the following vulnerability has been resolved: mmc: meson-gx: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, it will lead two issues: 1. The memory that allocated in mmc_alloc_host() is leaked. 2. In
- CVE-2022-50617Dec 8, 2025affected >= 5.11.0, < 5.15.86fixed 5.15.86
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/powerplay/psm: Fix memory leak in power state init Commit 902bc65de0b3 ("drm/amdgpu/powerplay/psm: return an error in power state init") made the power state init function return early in case of fai
- CVE-2022-50616Dec 8, 2025affected >= 3.18.0, < 6.0.16fixed 6.0.16
In the Linux kernel, the following vulnerability has been resolved: regulator: core: Use different devices for resource allocation and DT lookup Following by the below discussion, there's the potential UAF issue between regulator and mfd. https://lore.kernel.org/all/20221128143
- CVE-2022-50615Dec 8, 2025affected >= 5.3.0, < 5.10.163fixed 5.10.163
In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Fix reference count leak in snr_uncore_mmio_map() pci_get_device() will increase the reference count for the returned pci_dev, so snr_uncore_get_mc_dev() will return a pci_dev with its re
- CVE-2022-50614Dec 8, 2025affected >= 4.15.0, < 5.10.148fixed 5.10.148
In the Linux kernel, the following vulnerability has been resolved: misc: pci_endpoint_test: Fix pci_endpoint_test_{copy,write,read}() panic The dma_map_single() doesn't permit zero length mapping. It causes a follow panic. A panic was reported on arm64: [ 60.137988] ------
- CVE-2022-50583Dec 8, 2025affected >= 5.19.0, < 6.0.16fixed 6.0.16
In the Linux kernel, the following vulnerability has been resolved: md/raid0, raid10: Don't set discard sectors for request queue It should use disk_stack_limits to get a proper max_discard_sectors rather than setting a value by stack drivers. And there is a bug. If all member
- CVE-2025-40326Dec 8, 2025affected >= 6.14.0, < 6.17.8fixed 6.17.8
In the Linux kernel, the following vulnerability has been resolved: NFSD: Define actions for the new time_deleg FATTR4 attributes NFSv4 clients won't send legitimate GETATTR requests for these new attributes because they are intended to be used only with CB_GETATTR and SETATTR.
Page 67 of 88