Unity Linux 20.1050a / 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-396273)

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-396273 advisory. In the Linux kernel, the following vulnerability has been resolved: i2c: smbus: fix NULL function pointer dereference Baruch reported an OOPS when using the designwa...

Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986695)

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-986695 advisory. In the Linux kernel, the following vulnerability has been resolved: i2c: mlxbf: prevent stack overflow in mlxbfi2csmbusstarttransaction memcpy is called in a loop...

EUVD-2022-55397

Malicious code in bioql PyPI...

EUVD-2025-22660

Malicious code in bioql PyPI...

EUVD-2022-42506

Malicious code in bioql PyPI...

CVE-2025-39928

In the Linux kernel, the following vulnerability has been resolved: i2c: rtl9300: ensure data length is within supported range Add an explicit check for the xfer length to 'rtl9300i2cconfigxfer' to ensure the data length isn't within the supported range. In particular a data length of 0 is not...

CVE-2025-39928 i2c: rtl9300: ensure data length is within supported range

In the Linux kernel, the following vulnerability has been resolved: i2c: rtl9300: ensure data length is within supported range Add an explicit check for the xfer length to 'rtl9300i2cconfigxfer' to ensure the data length isn't within the supported range. In particular a data length of 0 is not...

CVE-2025-39928: Integer Underflow (Wrap or Wraparound)

In the Linux kernel, the following vulnerability has been resolved: i2c: rtl9300: ensure data length is within supported range Add an explicit check for the xfer length to 'rtl9300i2cconfigxfer' to ensure the data length isn't within the supported range. In particular a data length of 0 is not...

CVE-2022-50394 i2c: ismt: Fix an out-of-bounds bug in ismt_access()

In the Linux kernel, the following vulnerability has been resolved: i2c: ismt: Fix an out-of-bounds bug in ismtaccess When the driver does not check the data from the user, the variable 'data-block0' may be very large to cause an out-of-bounds bug. The following log can reveal it: 33.995542 i2c...

SUSE CVE-2025-39680

In the Linux kernel, the following vulnerability has been resolved: i2c: rtl9300: Fix out-of-bounds bug in rtl9300i2csmbusxfer The data-block0 variable comes from user. Without proper check, the variable may be very large to cause an out-of-bounds bug. Fix this bug by checking the value of...

CVE-2025-39680 i2c: rtl9300: Fix out-of-bounds bug in rtl9300_i2c_smbus_xfer

In the Linux kernel, the following vulnerability has been resolved: i2c: rtl9300: Fix out-of-bounds bug in rtl9300i2csmbusxfer The data-block0 variable comes from user. Without proper check, the variable may be very large to cause an out-of-bounds bug. Fix this bug by checking the value of...

PT-2025-36275

Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: The Linux kernel contains an out-of-bounds bug in the rtl9300 i2c smbus xfer function. The data-block0 variable, sourced from user input, lacks proper validation, potentially leading t...

CVE-2025-38425

In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: check msg length in SMBUS block read For SMBUS block read, do not continue to read if the message length passed from the device is '0' or greater than the maximum allowed bytes...

DEBIAN-CVE-2025-38425

In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: check msg length in SMBUS block read For SMBUS block read, do not continue to read if the message length passed from the device is '0' or greater than the maximum allowed bytes...

UBUNTU-CVE-2025-38425

In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: check msg length in SMBUS block read For SMBUS block read, do not continue to read if the message length passed from the device is '0' or greater than the maximum allowed bytes...

CVE-2025-38425 i2c: tegra: check msg length in SMBUS block read

In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: check msg length in SMBUS block read For SMBUS block read, do not continue to read if the message length passed from the device is '0' or greater than the maximum allowed bytes...

CVE-2025-38425

CVE-2025-38425 affects the Linux kernel i2c: tegra SMBUS block read path. Root cause: SMBUS block read reads the device-provided length without proper validation, continuing reads when length is 0 or exceeds allowed bytes. The vulnerability allows local attackers with lower privileges to potentia...

CVE-2025-38425

In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: check msg length in SMBUS block read For SMBUS block read, do not continue to read if the message length passed from the device is '0' or greater than the maximum allowed bytes...

CVE-2025-38425 i2c: tegra: check msg length in SMBUS block read

In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: check msg length in SMBUS block read For SMBUS block read, do not continue to read if the message length passed from the device is '0' or greater than the maximum allowed bytes...

CVE-2025-38425: Undefined Security Weakness

In the Linux kernel, the following vulnerability has been resolved: i2c: tegra: check msg length in SMBUS block read For SMBUS block read, do not continue to read if the message length passed from the device is '0' or greater than the maximum allowed bytes...