CVE-2024-48425

A segmentation fault SEGV was detected in the Assimp::SplitLargeMeshesProcessTriangle::UpdateNode function within the Assimp library during fuzz testing using AddressSanitizer. The crash occurs due to a read access violation at address 0x000000000460, which points to the zero page, indicating a...

CVE-2024-48426

A segmentation fault SEGV was detected in the SortByPTypeProcess::Execute function in the Assimp library during fuzz testing with AddressSanitizer. The crash occurred due to a read access to an invalid memory address 0x1000c9714971...

PT-2024-33105 · Assimp +2 · Assimp +2

Name of the Vulnerable Software and Affected Versions: Assimp affected versions not specified Description: A segmentation fault was detected in the Assimp::SplitLargeMeshesProcess Triangle::UpdateNode function within the Assimp library during fuzz testing using AddressSanitizer. The crash occurs...

PT-2024-33106

Name of the Vulnerable Software and Affected Versions Assimp library affected versions not specified Description A segmentation fault was detected in the SortByPTypeProcess::Execute function during fuzz testing with AddressSanitizer, caused by a read access to an invalid memory address...

CVE-2024-48426

A segmentation fault SEGV was detected in the SortByPTypeProcess::Execute function in the Assimp library during fuzz testing with AddressSanitizer. The crash occurred due to a read access to an invalid memory address 0x1000c9714971...

CVE-2024-48425

A segmentation fault SEGV was detected in the Assimp::SplitLargeMeshesProcessTriangle::UpdateNode function within the Assimp library during fuzz testing using AddressSanitizer. The crash occurs due to a read access violation at address 0x000000000460, which points to the zero page, indicating a...

CVE-2024-48425

A segmentation fault SEGV was detected in the Assimp::SplitLargeMeshesProcessTriangle::UpdateNode function within the Assimp library during fuzz testing using AddressSanitizer. The crash occurs due to a read access violation at address 0x000000000460, which points to the zero page, indicating a...

CVE-2024-48426

A segmentation fault SEGV was detected in the SortByPTypeProcess::Execute function in the Assimp library during fuzz testing with AddressSanitizer. The crash occurred due to a read access to an invalid memory address 0x1000c9714971...

CVE-2024-48425

A segmentation fault SEGV was detected in the Assimp::SplitLargeMeshesProcessTriangle::UpdateNode function within the Assimp library during fuzz testing using AddressSanitizer. The crash occurs due to a read access violation at address 0x000000000460, which points to the zero page, indicating a...

CVE-2024-48425: Buffer Copy without Checking Size of Input

A segmentation fault SEGV was detected in the Assimp::SplitLargeMeshesProcessTriangle::UpdateNode function within the Assimp library during fuzz testing using AddressSanitizer. The crash occurs due to a read access violation at address 0x000000000460, which points to the zero page, indicating a...

PT-2024-34058

Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.6.61 Description: The issue is related to a crash in the SPI driver when not using GPIO chip select. The problem occurs because a NULL pointer is passed to gpiod direction output when spi get csgpiod returns a...

PT-2024-36986

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The issue concerns the Linux kernel, specifically the powerpc/mm/fault component, where a problem with kfence page fault reporting has been resolved. The copy from kernel nofault functio...

TP-Link TL-WDR7660 DoS

The vulnerability of the wlanTimerRuleJsonToBin function in TP-Link TL-WDR7660 router software lies in the copying of buffers without checking the size of the input data. Exploiting this vulnerability could allow a malicious actor to trigger a service failure through a specially crafted HTTP...

CVE-2024-49887

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to don't panic system for no free segment fault injection f2fs: fix to don't panic system for no free segment fault injection syzbot reports a f2fs bug as below: F2FS-fs loop0: inject no free segment in getnewsegment of...

SUSE CVE-2022-49028

In the Linux kernel, the following vulnerability has been resolved: ixgbevf: Fix resource leak in ixgbevfinitmodule ixgbevfinitmodule won't destroy the workqueue created by createsinglethreadworkqueue when pciregisterdriver failed. Add destroyworkqueue in fail path to prevent the resource leak...

CVE-2024-49863

In the Linux kernel, the following vulnerability has been resolved: vhost/scsi: null-ptr-dereference in vhostscsigetreq Since commit 3f8ca2e115e5 "vhost/scsi: Extract common handling code from control queue handler" a null pointer dereference bug can be triggered when guest sends an SCSI AN...

CVE-2022-48971

A denial of service panic vulnerability was found in the Linux kernel's Bluetooth subsystem. When the btinit function call fails, btledscleanup is not called to unregister it, which can lead to a panic, resulting in the system's loss of availability. Mitigation Mitigation for this issue is either...

KLA74224 Multiple vulnerabilities in Google Chrome

Multiple vulnerabilities were found in Google Chrome. Malicious users can exploit these vulnerabilities to cause denial of service. Below is a complete list of vulnerabilities: 1. Inappropriate implementation vulnerability in Extensions can be exploited to cause denial of service. 2. Type confusi...

CVE-2024-50022

In the Linux kernel, the following vulnerability has been resolved: device-dax: correct pgoff align in daxsetmapping pgoff should be aligned using ALIGNDOWN instead of ALIGN. Otherwise, vmf-address not aligned to faultsize will be aligned to the next alignment, that can result in memory failure...

DEBIAN-CVE-2024-50022

In the Linux kernel, the following vulnerability has been resolved: device-dax: correct pgoff align in daxsetmapping pgoff should be aligned using ALIGNDOWN instead of ALIGN. Otherwise, vmf-address not aligned to faultsize will be aligned to the next alignment, that can result in memory failure...