1006 matches found
CVE-2023-54079
The CVE-2023-54079 issue affects the Linux kernel power: supply: bq27xxx driver. It describes two poll_interval related races during remove/unbind: previously poll_interval was set to 0 in bq27xxx_battery_teardown() to avoid requeuing the delayed_work item, which could randomly change poll_interv...
CVE-2022-50759
The CVE-2022-50759 issue affects Linux kernel media: i2c: ov5648, where the V4L2 fwnode data structure isn’t freed on unbind, causing a memory leak. The vulnerability, now resolved, is described across multiple sources as the V4L2 fwnode data not being freed on unbind, with patch references in st...
CVE-2022-50759 media: i2c: ov5648: Free V4L2 fwnode data on unbind
In the Linux kernel, the following vulnerability has been resolved: media: i2c: ov5648: Free V4L2 fwnode data on unbind The V4L2 fwnode data structure doesn't get freed on unbind, which leads to a memleak...
CVE-2023-54047 drm/rockchip: dw_hdmi: cleanup drm encoder during unbind
In the Linux kernel, the following vulnerability has been resolved: drm/rockchip: dwhdmi: cleanup drm encoder during unbind This fixes a use-after-free crash during rmmod. The DRM encoder is embedded inside the larger rockchiphdmi, which is allocated with the component. The component memory gets...
CVE-2023-54047
CVE-2023-54047 pertains to the Linux kernel’s DRM/rockchip subsystem, where a use-after-free crash can occur during module removal (rmmod) due to the rockchip_dw_hdmi encoder being torn down after its container, rather than cleaning up the encoder first. The root cause is the encoder being freed ...
CVE-2025-68730
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix page fault in ivpubounbindallbosfromcontext Don't add BO to the vdev-bolist in ivpugemcreateobject. When failure happens inside drmgemshmemcreate, the BO is not fully created and ivpugembofree callback will not be...
CVE-2025-68730
CVE-2025-68730 affects the Linux kernel’s accelerated graphics path (ivpu). The issue stems from an ivpu_bo_unbind_all_bos_from_context() page fault and an ivpu_gem_create_object() path that incorrectly adds BOs to vdev->bo_list; when drm_gem_shmem_create() fails, the BO may not be fully creat...
CVE-2025-68730 accel/ivpu: Fix page fault in ivpu_bo_unbind_all_bos_from_context()
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Fix page fault in ivpubounbindallbosfromcontext Don't add BO to the vdev-bolist in ivpugemcreateobject. When failure happens inside drmgemshmemcreate, the BO is not fully created and ivpugembofree callback will not be...
usb: renesas_usbhs: Fix synchronous external abort on unbind
...
PT-2025-53156
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A flaw exists in the Linux kernel related to the handling of poll interval within the bq27xxx battery driver. Specifically, the issue involves potential race conditions on device removal...
SUSE CVE-2025-68327
In the Linux kernel, the following vulnerability has been resolved: usb: renesasusbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usbfecm modprobe...
AZL-72883 CVE-2025-68327 affecting package kernel for versions less than 6.6.119.3-1
In the Linux kernel, the following vulnerability has been resolved: usb: renesasusbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usbfecm modprobe...
CVE-2025-68327
In the Linux kernel, the following vulnerability has been resolved: usb: renesasusbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usbfecm modprobe...
UBUNTU-CVE-2025-68327
In the Linux kernel, the following vulnerability has been resolved: usb: renesasusbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usbfecm modprobe...
CVE-2025-68327 usb: renesas_usbhs: Fix synchronous external abort on unbind
In the Linux kernel, the following vulnerability has been resolved: usb: renesasusbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usbfecm modprobe...
CVE-2025-68327
Summary (CVE-2025-68327) The Linux kernel fix mitigates a synchronous external abort in the Renesas usbhs driver when unbinding after a specific gadget configuration (Renesas RZ/G3S). The issue occurred because usbhs_sys_function_pullup could access IP registers after the USBHS clocks were disabl...
CVE-2025-68327 usb: renesas_usbhs: Fix synchronous external abort on unbind
In the Linux kernel, the following vulnerability has been resolved: usb: renesasusbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usbfecm modprobe...
CVE-2025-68327
In the Linux kernel, the following vulnerability has been resolved: usb: renesasusbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the configuration sequence described above: modprobe usbfecm modprobe...
Linux Distros Unpatched Vulnerability : CVE-2025-68327
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - usb: renesasusbhs: Fix synchronous external abort on unbind A synchronous external abort occurs on the Renesas RZ/G3S SoC if unbind is executed after the...
SUSE CVE-2025-68207
In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Synchronize Dead CT worker with unbind Cancel and wait for any Dead CT worker to complete before continuing with device unbinding. Else the worker will end up using resources freed by the undind operation. cherry pick...