DEBIAN-CVE-2024-42276

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: add missing condition check for existence of mapped data nvmemapdata is called when request has physical segments, hence the nvmeunmapdata should have same condition to avoid dereference...

CVE-2024-42276

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: add missing condition check for existence of mapped data nvmemapdata is called when request has physical segments, hence the nvmeunmapdata should have same condition to avoid dereference...

CVE-2024-42276

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: add missing condition check for existence of mapped data nvmemapdata is called when request has physical segments, hence the nvmeunmapdata should have same condition to avoid dereference...

CVE-2024-42276 nvme-pci: add missing condition check for existence of mapped data

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: add missing condition check for existence of mapped data nvmemapdata is called when request has physical segments, hence the nvmeunmapdata should have same condition to avoid dereference...

CVE-2024-42276

CVE-2024-42276 : The connected Astra Linux security bulletin confirms a Linux kernel vulnerability in the nvme-pci path was resolved by adding a missing condition check for the existence of mapped data. Specifically, nvme_map_data() is invoked when a request has physical segments, and nvme_unmap_...

CVE-2024-42276 nvme-pci: add missing condition check for existence of mapped data

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: add missing condition check for existence of mapped data nvmemapdata is called when request has physical segments, hence the nvmeunmapdata should have same condition to avoid dereference...

CVE-2024-42276 nvme-pci: add missing condition check for existence of mapped data

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: add missing condition check for existence of mapped data nvmemapdata is called when request has physical segments, hence the nvmeunmapdata should have same condition to avoid dereference...

CVE-2023-47165

Improper conditions check in the IntelR Data Center GPU Max Series 1100 and 1550 products may allow an privileged user to potentially enable denial of service via local access...

PT-2024-19067 · Intel · Intel Quartus Prime Lite Edition

Name of the Vulnerable Software and Affected Versions: IntelR QuartusR Prime Lite Edition Design software versions prior to 23.1 Description: The issue is related to an improper conditions check in the software, which may allow an authenticated user to potentially enable escalation of privilege v...

PT-2024-12157 · Intel · Intel Bios Ppam Firmware

Name of the Vulnerable Software and Affected Versions: IntelR BIOS PPAM firmware affected versions not specified Description: The issue is related to an improper conditions check in the IntelR BIOS PPAM firmware, which may allow a privileged user to potentially enable escalation of privilege via...

PT-2024-12727

Name of the Vulnerable Software and Affected Versions: IntelR Power Gadget software for macOS affected versions not specified Description: The issue is related to an improper conditions check in the IntelR Power Gadget software for macOS, which may allow an authenticated user to potentially enabl...

wrong sets of weth/dpxEth balance leads to incorrect calculation

Lines of code Vulnerability details impact In the curveSwap function, there is a crucial condition check to determine the values of a and b. If coin0 is equal to weth, the values should be set as 0, 1 or a, b. If not, they should be set as b, a. However, there is a discrepancy in the way these...

Mitigation of M-10: Issue not mitigated

MITIGATION IS NOT CONFIRMED MITIGATION IS NOT CONFIRMED Mitigation of M-10: Issue not mitigated Link to Issue: code-423n4/2023-03-asymmetry-findings363 Comments Even though the protocol team applied the warden's recommendation in M-10, the feature to enable/disable derivatives added as a mitigati...

Input validation

Improper condition check in some IntelR SPS firmware before version SPSE306.00.03.300.0 may allow a privileged user to potentially enable denial of service via local access...

CVE-2022-36794

Intel SPS firmware CVE-2022-36794: a root cause is an improper condition check in Intel SPS firmware prior to SPS_E3_06.00.03.300.0, which could allow a privileged user to cause a local denial of service. Affected versions are affected before the stated SPS_E3_06.00.03.300.0, and mitigation is to...

Intel SUR 代码问题漏洞

Intel SUR is a Software Asset Manager software from Intel Corporation USA. A security vulnerability exists in IntelR SUR version 2.4.8902, which stems from an improper condition check in the software that could allow a privileged user to covertly enable denial of service via network access...

Intel SPS 代码问题漏洞

Intel SPS is a server platform service from Intel Corporation USA. A security vulnerability exists in versions prior to IntelR SPS firmware SPSE306.00.03.300.0, which stems from an incorrect condition check. An attacker could exploit the vulnerability to cause a denial of service on the system...

PT-2023-13502 · Intel · Intel Sps Firmware

Name of the Vulnerable Software and Affected Versions: IntelR SPS firmware versions prior to SPS E3 06.00.03.300.0 Description: The issue is related to an improper condition check in the IntelR SPS firmware, which may allow a privileged user to potentially enable denial of service via local acces...

Input validation

Improper conditions check in some IntelR XMMTM 7560 Modem software before version M27560R01.2146.00 may allow a privileged user to potentially enable escalation of privilege via local access...

Issue with condition check handling

Lines of code Vulnerability details Impact It might cause data corruption, as most of the data handling is done in low level. Proof of Concept // Add up all the percents to make sure they cumulative are under 100%. uint256 percentTotal = 0; for uint256 i = 0; i typeuint56.max revert...