CVE-2024-46833 net: hns3: void array out of bound when loop tnl_num

In the Linux kernel, the following vulnerability has been resolved: net: hns3: void array out of bound when loop tnlnum When query reg inf of SSU, it loops tnlnum times. However, tnlnum comes from hardware and the length of array is a fixed value. To void array out of bound, make sure the loop ti...

CVE-2024-46833

In the Linux kernel, the following vulnerability has been resolved: net: hns3: void array out of bound when loop tnlnum When query reg inf of SSU, it loops tnlnum times. However, tnlnum comes from hardware and the length of array is a fixed value. To void array out of bound, make sure the loop ti...

CVE-2024-46832 MIPS: cevt-r4k: Don't call get_c0_compare_int if timer irq is installed

In the Linux kernel, the following vulnerability has been resolved: MIPS: cevt-r4k: Don't call getc0compareint if timer irq is installed This avoids warning: 0.118053 BUG: sleeping function called from invalid context at kernel/locking/mutex.c:283 Caused by getc0compareint on secondary CPU. We al...

CVE-2024-46832

CVE-2024-46832 involves the Linux kernel, specifically the MIPS cevt-r4k path. The issue arose when get_c0_compare_int was called if a timer IRQ was installed, which could trigger a WARN/BUG: sleeping function called from invalid context on secondary CPU. The patch changes the flow to avoid calli...

CVE-2024-46831 net: microchip: vcap: Fix use-after-free error in kunit test

In the Linux kernel, the following vulnerability has been resolved: net: microchip: vcap: Fix use-after-free error in kunit test This is a clear use-after-free error. We remove it, and rely on checking the return code of vcapdelrule...

CVE-2024-46831

In the Linux kernel, the following vulnerability has been resolved: net: microchip: vcap: Fix use-after-free error in kunit test This is a clear use-after-free error. We remove it, and rely on checking the return code of vcapdelrule...

CVE-2024-46830

In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Acquire kvm-srcu when handling KVMSETVCPUEVENTS Grab kvm-srcu when processing KVMSETVCPUEVENTS, as KVM will forcibly leave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX reads guest memory. Note,...

CVE-2024-46829 rtmutex: Drop rt_mutex::wait_lock before scheduling

In the Linux kernel, the following vulnerability has been resolved: rtmutex: Drop rtmutex::waitlock before scheduling rtmutexhandledeadlock is called with rtmutex::waitlock held. In the good case it returns with the lock held and in the deadlock case it emits a warning and goes into an endless...

CVE-2024-46829

The CVE-2024-46829 entry affects the Linux kernel and concerns a deadlock condition in rtmutex handling. Root cause: rt_mutex_handle_deadlock() is invoked with rt_mutex::wait_lock still held; in the deadlock path this could lead to an endless scheduling loop while the lock remains held and trigge...

CVE-2024-46828

In the Linux kernel, the following vulnerability has been resolved: sched: schcake: fix bulk flow accounting logic for host fairness In schcake, we keep track of the count of active bulk flows per host, when running in dst/src host fairness mode, which is used as the round-robin weight when...

CVE-2024-46829

In the Linux kernel, the following vulnerability has been resolved: rtmutex: Drop rtmutex::waitlock before scheduling rtmutexhandledeadlock is called with rtmutex::waitlock held. In the good case it returns with the lock held and in the deadlock case it emits a warning and goes into an endless...

CVE-2024-46827

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix firmware crash due to invalid peer nss Currently, if the access point receives an association request containing an Extended HE Capabilities Information Element with an invalid MCS-NSS, it triggers a firmware...

CVE-2024-46825

CVE-2024-46825 involves the Linux kernel wifi (iwlwifi mvm) where the firmware link ID is checked using WARN_ON() instead of IWL_FW_CHECK. The fix changes the lookup function iwl_mvm_rcu_fw_link_id_to_link_conf() to use IWL_FW_CHECK() when validating firmware-provided input. Public docs show this...

CVE-2024-46825

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: use IWLFWCHECK for link ID check The lookup function iwlmvmrcufwlinkidtolinkconf is normally called with input from the firmware, so it should use IWLFWCHECK instead of WARNON...

CVE-2024-46826

In the Linux kernel, the following vulnerability has been resolved: ELF: fix kernel.randomizevaspace double read ELF loader uses "randomizevaspace" twice. It is sysctl and can change at any moment, so 2 loads could see 2 different values in theory with unpredictable consequences. Issue exactly on...

CVE-2024-46822

In the Linux kernel, the following vulnerability has been resolved: arm64: acpi: Harden getcpuforacpiid against missing CPU entry In a review discussion of the changes to support vCPU hotplug where a check was added on the GICC being enabled if was online, it was noted that there is need to map...

CVE-2024-46821 drm/amd/pm: Fix negative array index read

In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: Fix negative array index read Avoid using the negative values for clkidex as an index into an array pptable-DpmDescriptor. V2: fix clkindex return check Tim Huang...

CVE-2024-46821

CVE-2024-46821 (Linux kernel, drm/amd/pm) affects the Linux kernel’s AMD power management code where a negative clk_index/clk_idex was used as an index into pptable->DpmDescriptor, leading to a negative array index read. The issue is resolved by a fix that prevents using negative values as an ...

CVE-2024-46821

In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: Fix negative array index read Avoid using the negative values for clkidex as an index into an array pptable-DpmDescriptor. V2: fix clkindex return check Tim Huang...

CVE-2024-46820

CVE-2024-46820 is a Linux kernel vulnerability in the AMDGPU VCN suspend path. The fix removes calls that disable IRQs and stops tracking IRQ state in vcn 5 suspend, because the code did not properly enable/disable VCN IRQs and did not manage IRQ state. The patch eliminates the WARN_ON(!amdgpu_ir...