CVE-2024-33220

CVE-2024-33220 affects AISuite3 v3.03.36 (ASUSTeK) via the AslO3_64.sys driver. The underlying issue is a vulnerability in AslO3_64.sys that allows privilege escalation and arbitrary code execution when handling crafted IOCTL requests. CVSS 3.1 metrics indicate HIGH impact on confidentiality, int...

CVE-2024-33220

An issue in the component AslO364.sys of ASUSTeK Computer Inc AISuite3 v3.03.36 3.03.36 allows attackers to escalate privileges and execute arbitrary code via sending crafted IOCTL requests...

CVE-2024-33219

CVE-2024-33219 affects the AsIO64.sys component in ASUSTeK (ASUS) SABERTOOTH X99 Driver v1.0.1.0. The issue allows local privilege escalation and arbitrary code execution via specially crafted IOCTL requests, with a CVSS v3.1 base score of 7.8 (Impact: Confidentiality, Integrity, Availability Hig...

CVE-2024-33218

An issue in the component AsUpIO64.sys of ASUSTeK Computer Inc ASUS USB 3.0 Boost Storage Driver 5.30.20.0 allows attackers to escalate privileges and execute arbitrary code via sending crafted IOCTL requests...

CVE-2024-33218

The CVE-2024-33218 entry concerns ASUSTeK Computer Inc.’s ASUS USB 3.0 Boost Storage Driver (version 5.30.20.0) and its AsUpIO64.sys component. The vulnerability allows attackers to escalate privileges and execute arbitrary code by sending crafted IOCTL requests, with local attack potential and h...

CVE-2021-47339

In the Linux kernel, the following vulnerability has been resolved: media: v4l2-core: explicitly clear ioctl input data As seen from a recent syzbot bug report, mistakes in the compat ioctl implementation can lead to uninitialized kernel stack data getting used as input for driver ioctl handlers...

CVE-2021-47364

In the Linux kernel, the following vulnerability has been resolved: comedi: Fix memory leak in compatinsnlist compatinsnlist handles the 32-bit version of the COMEDIINSNLIST ioctl whenwhen CONFIGCOMPAT is enabled. It allocates memory to temporarily hold an array of struct comediinsn converted fro...

CVE-2021-47383

In the Linux kernel, the following vulnerability has been resolved: tty: Fix out-of-bound vmalloc access in imageblit This issue happens when a userspace program does an ioctl FBIOPUTVSCREENINFO passing the fbvarscreeninfo struct containing only the fields xres, yres, and bitsperpixel with values...

kernel: a race out-of-bound read in vt

A race problem was seen in the vtkioctl in drivers/tty/vt/vtioctl.c in the Linux kernel, which may cause an out of bounds read in vt as the write access to vcmode is not protected by lock-in vtioctl KDSETMDE. The highest threat from this vulnerability is to data confidentiality...

kernel: use-after-free in read in vt_do_kdgkb_ioctl

A flaw was found in the Linux kernel. A use-after-free was found in the way the console subsystem was using ioctls KDGKBSENT and KDSKBSENT. A local user could use this flaw to get read memory access out of bounds. The highest threat from this vulnerability is to data confidentiality...

kernel: bluetooth: bt_sock_ioctl race condition leads to use-after-free in bt_sock_recvmsg

A flaw was found in the Bluetooth subsystem of the Linux kernel. A race condition between the btsockrecvmsg and btsockioctl functions could lead to a use-after-free on a socket buffer "skb". This flaw allows a local user to cause a denial of service condition or potential code execution...

kernel: ethtool: Fix uninitialized number of lanes

In the Linux kernel, the following vulnerability has been resolved: ethtool: Fix uninitialized number of lanes It is not possible to set the number of lanes when setting link modes using the legacy IOCTL ethtool interface. Since 'struct ethtoollinkksettings' is not initialized in this path, drive...

kernel: USB: usbtmc: Fix direction for 0-length ioctl control messages

A flaw was found in the Linux kernel’s USB Test and Measurement Class usbtmc driver. The driver did not properly validate the direction bit when handling ioctl calls for control messages with a length of zero. Under these circumstances, an incorrect direction can be submitted, leading to mismatch...

ASUS GPUTweak II 安全漏洞

ASUS GPUTweak II is a driver from Asus China Inc. It is used to drive more FPS. A security vulnerability exists in ASUS GPUTweak II version v1.4.5.2, which stems from a security flaw in the component IOMap64.sys. The vulnerability can be exploited by an attacker to elevate privileges and execute...

ASUS USB 安全漏洞

ASUS USB is a wireless adapter from Asus China. A security vulnerability exists in ASUS USB 3.0 Boost Storage Driver version 5.30.20.0, which originates from a problem with the component AsUpIO64.sys and allows attackers to elevate privileges and execute arbitrary code by sending a crafted IOCTL...

ASUS ATSZIO Driver 安全漏洞

ASUS ATSZIO Driver is a driver from Asus China. A security vulnerability exists in ASUS ATSZIO Driver version v0.2.1.7, which originates from a security flaw in the component ATSZIO 64.sys. The vulnerability can be exploited by an attacker to elevate privileges and execute arbitrary code by sendi...

Insyde Software Corp SEG Windows Driver 安全漏洞

Insyde Software Corp SEG Windows Driver is a driver for managing and processing system events from Insyde Software Corp China. A security vulnerability exists in Insyde Software Corp SEG Windows Driver version v100.00.07.02, which originates from a security flaw in the component segwindrvx64.sys...

CVE-2023-52705

CVE-2023-52705 is a kernel vulnerability affecting the nilfs2 filesystem code in Linux. The issue is an underflow/incorrect boundary calculation in NILFS_SB2_OFFSET_BYTES that computes the position of the second superblock, which can underflow when the device size is smaller than 4096 bytes. This...

CVE-2021-47339

In the Linux kernel, the following vulnerability has been resolved: media: v4l2-core: explicitly clear ioctl input data As seen from a recent syzbot bug report, mistakes in the compat ioctl implementation can lead to uninitialized kernel stack data getting used as input for driver ioctl handlers...

CVE-2021-47339

In the Linux kernel, the following vulnerability has been resolved: media: v4l2-core: explicitly clear ioctl input data As seen from a recent syzbot bug report, mistakes in the compat ioctl implementation can lead to uninitialized kernel stack data getting used as input for driver ioctl handlers...