Ralf Spenneberg

The issue is related to the `ext4 fill super` function in the Linux kernel, which does not properly validate meta block groups. This allows physically proximate attackers to cause a denial of service, resulting in an out-of-bounds read and system crash, via a crafted ext4 image.

The issue allows physically proximate attackers to cause a denial of service, resulting in a system crash due to a NULL pointer dereference. This is achieved by using a crafted endpoints value in a USB device descriptor.

The issue allows physically proximate attackers to cause a denial of service, resulting in a NULL pointer dereference and system crash. This is achieved via a crafted `endpoints` value in a USB device descriptor, specifically targeting the `digi port init` function in the Linux kernel.

The issue allows physically proximate attackers to cause a denial of service, resulting in a system crash due to a NULL pointer dereference. This is achieved by using a crafted `endpoints` value in a USB device descriptor.

The issue allows physically proximate attackers to cause a denial of service, resulting in a system crash due to a NULL pointer dereference. This is achieved by using a crafted `endpoints` value in a USB device descriptor.

The issue allows physically proximate attackers to cause a denial of service, resulting in a NULL pointer dereference and system crash, via a crafted USB device without two interrupt-in endpoint descriptors. This is due to a problem in the `mct u232 msr to state` function.

The issue allows physically proximate attackers to cause a denial of service, resulting in a NULL pointer dereference and system crash, via a USB device without both an interrupt-in and an interrupt-out endpoint descriptor. This is related to the `cypress generic port probe` and `cypress open` functions.

The issue allows physically proximate attackers to cause a denial of service, resulting in a NULL pointer dereference and system crash, via a USB device without both a control and a data endpoint descriptor. This is due to a problem in the acm probe function in drivers/usb/class/cdc-acm.c.

The issue is related to the iowarrior probe function in the Linux kernel, which contains an error in handling USB device descriptors. This can be exploited by an attacker to cause a denial of service, resulting in a system crash due to a NULL pointer dereference. The exploitation requires physical proximity to the system and involves crafting a specific value in the USB device descriptor.

The issue allows remote attackers to bypass a user program block protection mechanism.

The issue allows physically proximate attackers to cause a denial of service, potentially leading to a system crash, by inserting a USB device that lacks specific endpoints.

The issue allows physically proximate attackers to cause a denial of service, potentially leading to a system crash, by inserting a USB device that lacks a bulk-out endpoint. This is due to a NULL pointer dereference in the `clie 5 attach` function.

The issue allows physically proximate attackers to cause a denial of service, resulting in a NULL pointer dereference and system crash, via a crafted USB device that lacks endpoints. This is due to a problem in the aiptek probe function in drivers/input/tablet/aiptek.c.

The issue is related to errors in the code of the usbvision driver in the Linux kernel. It allows an attacker with physical access to cause a denial of service (panic) by setting a nonzero `bInterfaceNumber` value in a USB device descriptor.

The issue allows remote attackers to cause a denial of service, resulting in a device outage, by sending a long parameter to the HTTP application.

A cross-site request forgery (CSRF) issue exists, allowing remote attackers to hijack the authentication of victims via unknown vectors.

The issue allows physically proximate attackers to cause a denial of service, resulting in a NULL pointer dereference and system crash. This is achieved via a crafted endpoints value in a USB device descriptor, specifically targeting the wacom probe function in drivers/input/tablet/wacom sys.c.