The vulnerability of the bond_do_ioctl() function in the drivers/net/bonding/bond_main.c file of the Linux kernel network device driver allows a attacker to cause a service failure.

The vulnerability of the bonddoioctl function in the drivers/net/bonding/bondmain.c file of the Linux kernel network device driver is related to the use of pointers. Exploiting this vulnerability could allow a remote attacker to cause service interruptions...

CVE-2026-53337

In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix NULL pointer dereference in bonddoioctl In bonddoioctl, slavedev is obtained via devgetbyname which can return NULL if the requested interface name does not exist. However, the subsequent slavedbg call is placed...

UBUNTU-CVE-2026-53337

In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix NULL pointer dereference in bonddoioctl In bonddoioctl, slavedev is obtained via devgetbyname which can return NULL if the requested interface name does not exist. However, the subsequent slavedbg call is placed...

CVE-2026-53337

CVE-2026-53337 affects the Linux kernel bonding code. In bond_do_ioctl(), slave_dev is obtained via __dev_get_by_name() and may be NULL, yet slave_dbg(bond_dev, slave_dev, …) dereferences slave_dev->name before the NULL check, causing a NULL pointer dereference and a potential local DoS when a...

CVE-2026-53337 net: bonding: fix NULL pointer dereference in bond_do_ioctl()

In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix NULL pointer dereference in bonddoioctl In bonddoioctl, slavedev is obtained via devgetbyname which can return NULL if the requested interface name does not exist. However, the subsequent slavedbg call is placed...

CVE-2026-53337

In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix NULL pointer dereference in bonddoioctl In bonddoioctl, slavedev is obtained via devgetbyname which can return NULL if the requested interface name does not exist. However, the subsequent slavedbg call is placed...