Show filters
5,420 Total Results
Displaying 171-180 of 5,420
Sort by:
Attacker Value
Unknown
CVE-2024-0607
Disclosure Date: January 18, 2024 (last updated April 25, 2024)
A flaw was found in the Netfilter subsystem in the Linux kernel. The issue is in the nft_byteorder_eval() function, where the code iterates through a loop and writes to the `dst` array. On each iteration, 8 bytes are written, but `dst` is an array of u32, so each element only has space for 4 bytes. That means every iteration overwrites part of the previous element corrupting this array of u32. This flaw allows a local user to cause a denial of service or potentially break NetFilter functionality.
0
Attacker Value
Unknown
CVE-2024-0409
Disclosure Date: January 18, 2024 (last updated May 22, 2024)
A flaw was found in the X.Org server. The cursor code in both Xephyr and Xwayland uses the wrong type of private at creation. It uses the cursor bits type with the cursor as private, and when initiating the cursor, that overwrites the XSELINUX context.
0
Attacker Value
Unknown
CVE-2024-0408
Disclosure Date: January 18, 2024 (last updated May 22, 2024)
A flaw was found in the X.Org server. The GLX PBuffer code does not call the XACE hook when creating the buffer, leaving it unlabeled. When the client issues another request to access that resource (as with a GetGeometry) or when it creates another resource that needs to access that buffer, such as a GC, the XSELINUX code will try to use an object that was never labeled and crash because the SID is NULL.
0
Attacker Value
Unknown
CVE-2023-6816
Disclosure Date: January 18, 2024 (last updated April 25, 2024)
A flaw was found in X.Org server. Both DeviceFocusEvent and the XIQueryPointer reply contain a bit for each logical button currently down. Buttons can be arbitrarily mapped to any value up to 255, but the X.Org Server was only allocating space for the device's particular number of buttons, leading to a heap overflow if a bigger value was used.
0
Attacker Value
Unknown
CVE-2024-0646
Disclosure Date: January 17, 2024 (last updated August 28, 2024)
An out-of-bounds memory write flaw was found in the Linux kernel’s Transport Layer Security functionality in how a user calls a function splice with a ktls socket as the destination. This flaw allows a local user to crash or potentially escalate their privileges on the system.
0
Attacker Value
Unknown
CVE-2024-0641
Disclosure Date: January 17, 2024 (last updated April 25, 2024)
A denial of service vulnerability was found in tipc_crypto_key_revoke in net/tipc/crypto.c in the Linux kernel’s TIPC subsystem. This flaw allows guests with local user privileges to trigger a deadlock and potentially crash the system.
0
Attacker Value
Unknown
CVE-2024-0639
Disclosure Date: January 17, 2024 (last updated April 25, 2024)
A denial of service vulnerability due to a deadlock was found in sctp_auto_asconf_init in net/sctp/socket.c in the Linux kernel’s SCTP subsystem. This flaw allows guests with local user privileges to trigger a deadlock and potentially crash the system.
0
Attacker Value
Unknown
CVE-2024-0232
Disclosure Date: January 16, 2024 (last updated April 25, 2024)
A heap use-after-free issue has been identified in SQLite in the jsonParseAddNodeArray() function in sqlite3.c. This flaw allows a local attacker to leverage a victim to pass specially crafted malicious input to the application, potentially causing a crash and leading to a denial of service.
0
Attacker Value
Unknown
CVE-2024-0553
Disclosure Date: January 16, 2024 (last updated July 08, 2024)
A vulnerability was found in GnuTLS. The response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from the response times of ciphertexts with correct PKCS#1 v1.5 padding. This issue may allow a remote attacker to perform a timing side-channel attack in the RSA-PSK key exchange, potentially leading to the leakage of sensitive data. CVE-2024-0553 is designated as an incomplete resolution for CVE-2023-5981.
0
Attacker Value
Unknown
CVE-2024-0562
Disclosure Date: January 15, 2024 (last updated August 28, 2024)
A use-after-free flaw was found in the Linux Kernel. When a disk is removed, bdi_unregister is called to stop further write-back and waits for associated delayed work to complete. However, wb_inode_writeback_end() may schedule bandwidth estimation work after this has completed, which can result in the timer attempting to access the recently freed bdi_writeback.
0