https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 27 Oct 2026 07:53:08 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-99069 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: ati_remote2 - fix type confusion in device attribute handlers</p> <p>Previously, the channel_mask and mode_mask attributes were registered on the parent usb_device via sysfs_create_group(). When commit b20d6bf8014b (&#34;Input: ati-remote2 - use driver core to instantiate device attributes&#34;) converted the driver to let the driver core manage them via dev_groups in struct usb_driver, the attributes moved to the bound usb_interface devices, but the show and store callbacks were not updated accordingly.</p> <p>As a result, the callbacks still invoked to_usb_device() on a device pointer belonging to a struct usb_interface, producing an invalid usb_device pointer.</p> <p>Use to_usb_interface() directly in the attribute handlers to obtain the interface and its driver data.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: ati_remote2 - fix type confusion in device attribute handlers</p> <p>Previously, the channel_mask and mode_mask attributes were registered on the parent usb_device via sysfs_create_group(). When commit b20d6bf8014b (&#34;Input: ati-remote2 - use driver core to instantiate device attributes&#34;) converted the driver to let the driver core manage them via dev_groups in struct usb_driver, the attributes moved to the bound usb_interface devices, but the show and store callbacks were not updated accordingly.</p> <p>As a result, the callbacks still invoked to_usb_device() on a device pointer belonging to a struct usb_interface, producing an invalid usb_device pointer.</p> <p>Use to_usb_interface() directly in the attribute handlers to obtain the interface and its driver data.</p> https://db.gcve.eu/vuln/fkie_cve-2026-99069 https://db.gcve.eu/vuln/ghsa-5wgj-7vcp-vw5x <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: ati_remote2 - fix type confusion in device attribute handlers</p> <p>Previously, the channel_mask and mode_mask attributes were registered on the parent usb_device via sysfs_create_group(). When commit b20d6bf8014b (&#34;Input: ati-remote2 - use driver core to instantiate device attributes&#34;) converted the driver to let the driver core manage them via dev_groups in struct usb_driver, the attributes moved to the bound usb_interface devices, but the show and store callbacks were not updated accordingly.</p> <p>As a result, the callbacks still invoked to_usb_device() on a device pointer belonging to a struct usb_interface, producing an invalid usb_device pointer.</p> <p>Use to_usb_interface() directly in the attribute handlers to obtain the interface and its driver data.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>Input: ati_remote2 - fix type confusion in device attribute handlers</p> <p>Previously, the channel_mask and mode_mask attributes were registered on the parent usb_device via sysfs_create_group(). When commit b20d6bf8014b (&#34;Input: ati-remote2 - use driver core to instantiate device attributes&#34;) converted the driver to let the driver core manage them via dev_groups in struct usb_driver, the attributes moved to the bound usb_interface devices, but the show and store callbacks were not updated accordingly.</p> <p>As a result, the callbacks still invoked to_usb_device() on a device pointer belonging to a struct usb_interface, producing an invalid usb_device pointer.</p> <p>Use to_usb_interface() directly in the attribute handlers to obtain the interface and its driver data.</p> https://db.gcve.eu/vuln/ghsa-5wgj-7vcp-vw5x https://db.gcve.eu/vuln/msrc_cve-2026-99069 msrc_CVE-2026-99069 https://db.gcve.eu/vuln/msrc_cve-2026-99069 https://db.gcve.eu/vuln/ubuntu-cve-2026-99069 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 257 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Input: ati_remote2 - fix type confusion in device attribute handlers Previously, the channel_mask and mode_mask attributes were registered on the parent usb_device via sysfs_create_group(). When commit b20d6bf8014b (&#34;Input: ati-remote2 - use driver core to instantiate device attributes&#34;) converted the driver to let the driver core manage them via dev_groups in struct usb_driver, the attributes moved to the bound usb_interface devices, but the show and store callbacks were not updated accordingly. As a result, the callbacks still invoked to_usb_device() on a device pointer belonging to a struct usb_interface, producing an invalid usb_device pointer. Use to_usb_interface() directly in the attribute handlers to obtain the interface and its driver data.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 257 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: Input: ati_remote2 - fix type confusion in device attribute handlers Previously, the channel_mask and mode_mask attributes were registered on the parent usb_device via sysfs_create_group(). When commit b20d6bf8014b (&#34;Input: ati-remote2 - use driver core to instantiate device attributes&#34;) converted the driver to let the driver core manage them via dev_groups in struct usb_driver, the attributes moved to the bound usb_interface devices, but the show and store callbacks were not updated accordingly. As a result, the callbacks still invoked to_usb_device() on a device pointer belonging to a struct usb_interface, producing an invalid usb_device pointer. Use to_usb_interface() directly in the attribute handlers to obtain the interface and its driver data.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-99069