Vulnerabilities (CVE)

Total 82132 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-50129 1 Linux 1 Linux Kernel 2024-11-07 N/A 7.8 HIGH
In the Linux kernel, the following vulnerability has been resolved: net: pse-pd: Fix out of bound for loop Adjust the loop limit to prevent out-of-bounds access when iterating over PI structures. The loop should not reach the index pcdev->nr_lines since we allocate exactly pcdev->nr_lines number of PI structures. This fix ensures proper bounds are maintained during iterations.
CVE-2024-51523 1 Huawei 1 Harmonyos 2024-11-07 N/A 7.5 HIGH
Information management vulnerability in the Gallery module Impact: Successful exploitation of this vulnerability may affect service confidentiality.
CVE-2024-38406 1 Qualcomm 88 Aqt1000, Aqt1000 Firmware, Fastconnect 6200 and 85 more 2024-11-07 N/A 7.0 HIGH
Memory corruption while handling IOCTL calls in JPEG Encoder driver.
CVE-2024-38424 1 Qualcomm 238 Ar8035, Ar8035 Firmware, Fastconnect 6200 and 235 more 2024-11-07 N/A 7.8 HIGH
Memory corruption during GNSS HAL process initialization.
CVE-2024-38423 1 Qualcomm 412 205 Mobile Platform, 205 Mobile Platform Firmware, 215 Mobile Platform and 409 more 2024-11-07 N/A 7.8 HIGH
Memory corruption while processing GPU page table switch.
CVE-2024-38422 1 Qualcomm 536 205 Mobile Platform, 205 Mobile Platform Firmware, 215 Mobile Platform and 533 more 2024-11-07 N/A 7.8 HIGH
Memory corruption while processing voice packet with arbitrary data received from ADSP.
CVE-2024-38421 1 Qualcomm 154 Fastconnect 6200, Fastconnect 6200 Firmware, Fastconnect 7800 and 151 more 2024-11-07 N/A 7.8 HIGH
Memory corruption while processing GPU commands.
CVE-2024-38419 1 Qualcomm 296 Ar8035, Ar8035 Firmware, Csra6620 and 293 more 2024-11-07 N/A 7.8 HIGH
Memory corruption while invoking IOCTL calls from the use-space for HGSL memory node.
CVE-2024-38415 1 Qualcomm 356 215 Mobile Platform, 215 Mobile Platform Firmware, Ar8035 and 353 more 2024-11-07 N/A 7.8 HIGH
Memory corruption while handling session errors from firmware.
CVE-2024-38410 1 Qualcomm 50 Fastconnect 6700, Fastconnect 6700 Firmware, Fastconnect 6900 and 47 more 2024-11-07 N/A 7.8 HIGH
Memory corruption while IOCLT is called when device is in invalid state and the WMI command buffer may be freed twice.
CVE-2024-38409 1 Qualcomm 50 Fastconnect 6700, Fastconnect 6700 Firmware, Fastconnect 6900 and 47 more 2024-11-07 N/A 7.8 HIGH
Memory corruption while station LL statistic handling.
CVE-2024-38407 1 Qualcomm 88 Aqt1000, Aqt1000 Firmware, Fastconnect 6200 and 85 more 2024-11-07 N/A 7.0 HIGH
Memory corruption while processing input parameters for any IOCTL call in the JPEG Encoder driver.
CVE-2024-33033 1 Qualcomm 56 Fastconnect 6900, Fastconnect 6900 Firmware, Fastconnect 7800 and 53 more 2024-11-07 N/A 7.8 HIGH
Memory corruption while processing IOCTL calls to unmap the buffers.
CVE-2022-48991 1 Linux 1 Linux Kernel 2024-11-07 N/A 7.8 HIGH
In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don't keep accessing pages which aren't mapped anymore. Secondary MMUs don't hold their own references to pages that are mirrored over, so failing to notify them can lead to page use-after-free. I'm marking this as addressing an issue introduced in commit f3f0e1d2150b ("khugepaged: add support of collapse for tmpfs/shmem pages"), but most of the security impact of this only came in commit 27e1f8273113 ("khugepaged: enable collapse pmd for pte-mapped THP"), which actually omitted flushes for the removal of present PTEs, not just for the removal of empty page tables.
CVE-2024-50005 1 Linux 1 Linux Kernel 2024-11-07 N/A 7.8 HIGH
In the Linux kernel, the following vulnerability has been resolved: mac802154: Fix potential RCU dereference issue in mac802154_scan_worker In the `mac802154_scan_worker` function, the `scan_req->type` field was accessed after the RCU read-side critical section was unlocked. According to RCU usage rules, this is illegal and can lead to unpredictable behavior, such as accessing memory that has been updated or causing use-after-free issues. This possible bug was identified using a static analysis tool developed by myself, specifically designed to detect RCU-related issues. To address this, the `scan_req->type` value is now stored in a local variable `scan_req_type` while still within the RCU read-side critical section. The `scan_req_type` is then used after the RCU lock is released, ensuring that the type value is safely accessed without violating RCU rules.
CVE-2024-10805 1 Anisha 1 University Event Management System 2024-11-07 6.5 MEDIUM 8.8 HIGH
A vulnerability was found in code-projects University Event Management System 1.0. It has been classified as critical. This affects an unknown part of the file doedit.php. The manipulation of the argument id leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The initial researcher advisory mentions a confusing product name to be affected. Other parameters might be affected as well.
CVE-2022-48998 1 Linux 1 Linux Kernel 2024-11-07 N/A 7.8 HIGH
In the Linux kernel, the following vulnerability has been resolved: powerpc/bpf/32: Fix Oops on tail call tests test_bpf tail call tests end up as: test_bpf: #0 Tail call leaf jited:1 85 PASS test_bpf: #1 Tail call 2 jited:1 111 PASS test_bpf: #2 Tail call 3 jited:1 145 PASS test_bpf: #3 Tail call 4 jited:1 170 PASS test_bpf: #4 Tail call load/store leaf jited:1 190 PASS test_bpf: #5 Tail call load/store jited:1 BUG: Unable to handle kernel data access on write at 0xf1b4e000 Faulting instruction address: 0xbe86b710 Oops: Kernel access of bad area, sig: 11 [#1] BE PAGE_SIZE=4K MMU=Hash PowerMac Modules linked in: test_bpf(+) CPU: 0 PID: 97 Comm: insmod Not tainted 6.1.0-rc4+ #195 Hardware name: PowerMac3,1 750CL 0x87210 PowerMac NIP: be86b710 LR: be857e88 CTR: be86b704 REGS: f1b4df20 TRAP: 0300 Not tainted (6.1.0-rc4+) MSR: 00009032 <EE,ME,IR,DR,RI> CR: 28008242 XER: 00000000 DAR: f1b4e000 DSISR: 42000000 GPR00: 00000001 f1b4dfe0 c11d2280 00000000 00000000 00000000 00000002 00000000 GPR08: f1b4e000 be86b704 f1b4e000 00000000 00000000 100d816a f2440000 fe73baa8 GPR16: f2458000 00000000 c1941ae4 f1fe2248 00000045 c0de0000 f2458030 00000000 GPR24: 000003e8 0000000f f2458000 f1b4dc90 3e584b46 00000000 f24466a0 c1941a00 NIP [be86b710] 0xbe86b710 LR [be857e88] __run_one+0xec/0x264 [test_bpf] Call Trace: [f1b4dfe0] [00000002] 0x2 (unreliable) Instruction dump: XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX ---[ end trace 0000000000000000 ]--- This is a tentative to write above the stack. The problem is encoutered with tests added by commit 38608ee7b690 ("bpf, tests: Add load store test case for tail call") This happens because tail call is done to a BPF prog with a different stack_depth. At the time being, the stack is kept as is when the caller tail calls its callee. But at exit, the callee restores the stack based on its own properties. Therefore here, at each run, r1 is erroneously increased by 32 - 16 = 16 bytes. This was done that way in order to pass the tail call count from caller to callee through the stack. As powerpc32 doesn't have a red zone in the stack, it was necessary the maintain the stack as is for the tail call. But it was not anticipated that the BPF frame size could be different. Let's take a new approach. Use register r4 to carry the tail call count during the tail call, and save it into the stack at function entry if required. This means the input parameter must be in r3, which is more correct as it is a 32 bits parameter, then tail call better match with normal BPF function entry, the down side being that we move that input parameter back and forth between r3 and r4. That can be optimised later. Doing that also has the advantage of maximising the common parts between tail calls and a normal function exit. With the fix, tail call tests are now successfull: test_bpf: #0 Tail call leaf jited:1 53 PASS test_bpf: #1 Tail call 2 jited:1 115 PASS test_bpf: #2 Tail call 3 jited:1 154 PASS test_bpf: #3 Tail call 4 jited:1 165 PASS test_bpf: #4 Tail call load/store leaf jited:1 101 PASS test_bpf: #5 Tail call load/store jited:1 141 PASS test_bpf: #6 Tail call error path, max count reached jited:1 994 PASS test_bpf: #7 Tail call count preserved across function calls jited:1 140975 PASS test_bpf: #8 Tail call error path, NULL target jited:1 110 PASS test_bpf: #9 Tail call error path, index out of range jited:1 69 PASS test_bpf: test_tail_calls: Summary: 10 PASSED, 0 FAILED, [10/10 JIT'ed]
CVE-2024-10711 1 Ithemelandco 1 Woocommerce Report 2024-11-07 N/A 8.8 HIGH
The WooCommerce Report plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.5.1. This is due to missing or incorrect nonce validation on the settings update functionality. This makes it possible for unauthenticated attackers to update arbitrary options that can be leveraged for privilege escalation via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CVE-2024-50456 1 Seopress 1 Seopress 2024-11-07 N/A 8.8 HIGH
Missing Authorization vulnerability in The SEO Guys at SEOPress SEOPress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SEOPress: from n/a through 8.1.1.
CVE-2024-50455 1 Seopress 1 Seopress 2024-11-07 N/A 8.8 HIGH
Missing Authorization vulnerability in The SEO Guys at SEOPress SEOPress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects SEOPress: from n/a through 8.1.1.