In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6xxx: Correct check for empty list Since commit a3c53be55c95 ("net: dsa: mv88e6xxx: Support multiple MDIO busses") mv88e6xxx_default_mdio_bus() has checked that the return value of list_first_entry() is non-NULL. This appears to be intended to guard against the list chip->mdios being empty. However, it is not the correct check as the implementation of list_first_entry is not designed to return NULL for empty lists. Instead, use list_first_entry_or_null() which does return NULL if the list is empty. Flagged by Smatch. Compile tested only.
{
"binaries": [
{
"binary_name": "block-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "block-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "crypto-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "crypto-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "dasd-extra-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "dasd-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fat-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fat-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "firewire-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "floppy-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-core-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-secondary-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "fs-secondary-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "input-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "input-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ipmi-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ipmi-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "irda-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "irda-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "kernel-image-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "kernel-image-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-cloud-tools-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-tools-4.15.0-23",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-udebs-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-hwe-edge-udebs-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-source-4.15.0",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-generic",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-generic-lpae",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-23-lowlatency",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "md-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "md-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "message-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "mouse-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "mouse-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "multipath-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "multipath-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nfs-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nfs-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-shared-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-shared-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-usb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "nic-usb-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "parport-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "parport-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pata-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pcmcia-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "plip-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "plip-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ppp-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "ppp-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "sata-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "sata-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "scsi-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "scsi-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "serial-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "storage-core-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "storage-core-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "usb-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "usb-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "virtio-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "vlan-modules-4.15.0-23-generic-di",
"binary_version": "4.15.0-23.25~16.04.1"
},
{
"binary_name": "vlan-modules-4.15.0-23-generic-lpae-di",
"binary_version": "4.15.0-23.25~16.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-5.0-tools-5.0.0-1027",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-aws-headers-5.0.0-1027",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-buildinfo-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-headers-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-image-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-modules-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-modules-extra-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
},
{
"binary_name": "linux-tools-5.0.0-1027-aws",
"binary_version": "5.0.0-1027.30"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-5.3-cloud-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-aws-5.3-headers-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-aws-5.3-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-buildinfo-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-cloud-tools-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-headers-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-image-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-modules-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-modules-extra-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
},
{
"binary_name": "linux-tools-5.3.0-1035-aws",
"binary_version": "5.3.0-1035.37"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-azure-headers-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-azure-tools-5.0.0-1036",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-buildinfo-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-headers-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-modules-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-modules-extra-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
},
{
"binary_name": "linux-tools-5.0.0-1036-azure",
"binary_version": "5.0.0-1036.38"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-5.3-cloud-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-azure-5.3-headers-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-azure-5.3-tools-5.3.0-1035",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-buildinfo-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-cloud-tools-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-headers-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-modules-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-modules-extra-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
},
{
"binary_name": "linux-tools-5.3.0-1035-azure",
"binary_version": "5.3.0-1035.36"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-edge-cloud-tools-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-azure-edge-tools-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-azure-headers-5.0.0-1012",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-headers-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-modules-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-modules-extra-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
},
{
"binary_name": "linux-tools-5.0.0-1012-azure",
"binary_version": "5.0.0-1012.12~18.04.2"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-gcp-headers-5.0.0-1034",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-gcp-tools-5.0.0-1034",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-headers-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-modules-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-modules-extra-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
},
{
"binary_name": "linux-tools-5.0.0-1034-gcp",
"binary_version": "5.0.0-1034.35"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-gcp-5.3-headers-5.3.0-1032",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-gcp-5.3-tools-5.3.0-1032",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-headers-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-modules-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
},
{
"binary_name": "linux-tools-5.3.0-1032-gcp",
"binary_version": "5.3.0-1032.34~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-gke-4.15-headers-4.15.0-1079",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-gke-4.15-tools-4.15.0-1079",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-headers-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-modules-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-modules-extra-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
},
{
"binary_name": "linux-tools-4.15.0-1079-gke",
"binary_version": "4.15.0-1079.84"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-gke-5.4-headers-5.4.0-1080",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-gke-5.4-tools-5.4.0-1080",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1080-gke",
"binary_version": "5.4.0-1080.86~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-cloud-tools-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-headers-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-source-5.4.0",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-gkeop-5.4-tools-5.4.0-1051",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1051-gkeop",
"binary_version": "5.4.0-1051.54~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "block-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "crypto-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fat-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "firewire-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "floppy-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fs-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "fs-secondary-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "input-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "ipmi-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "kernel-image-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-buildinfo-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-buildinfo-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-cloud-tools-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-cloud-tools-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-headers-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-headers-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-cloud-tools-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-headers-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-tools-5.3.0-76",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-hwe-udebs-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-unsigned-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-image-unsigned-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-modules-extra-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-source-5.3.0",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-tools-5.3.0-76-generic",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "linux-tools-5.3.0-76-lowlatency",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "md-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "message-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "mouse-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "multipath-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nfs-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-pcmcia-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-shared-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "nic-usb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "parport-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pata-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pcmcia-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "pcmcia-storage-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "plip-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "ppp-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "sata-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "scsi-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "serial-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "storage-core-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "usb-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "virtio-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
},
{
"binary_name": "vlan-modules-5.3.0-76-generic-di",
"binary_version": "5.3.0-76.72"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "block-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "block-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "crypto-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "crypto-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "dasd-extra-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "dasd-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fat-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fat-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "firewire-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "floppy-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-core-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-secondary-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "fs-secondary-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "input-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "input-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ipmi-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ipmi-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "kernel-image-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "kernel-image-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-buildinfo-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-cloud-tools-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-headers-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-cloud-tools-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-tools-5.3.0-24",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-udebs-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-hwe-edge-udebs-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-image-unsigned-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-modules-extra-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-source-5.3.0",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-generic",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-generic-lpae",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "linux-tools-5.3.0-24-lowlatency",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "md-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "md-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "message-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "mouse-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "mouse-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "multipath-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "multipath-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nfs-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nfs-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-pcmcia-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-shared-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-shared-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-usb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "nic-usb-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "parport-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "parport-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pata-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pcmcia-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "pcmcia-storage-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "plip-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "plip-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ppp-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "ppp-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "sata-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "sata-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "scsi-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "scsi-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "serial-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "storage-core-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "storage-core-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "usb-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "usb-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "virtio-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "vlan-modules-5.3.0-24-generic-di",
"binary_version": "5.3.0-24.26~18.04.2"
},
{
"binary_name": "vlan-modules-5.3.0-24-generic-lpae-di",
"binary_version": "5.3.0-24.26~18.04.2"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "block-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "crypto-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fat-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "firewire-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "floppy-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fs-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "fs-secondary-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "input-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "ipmi-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "irda-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "kernel-image-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-buildinfo-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-headers-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-modules-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-oem-headers-4.15.0-1103",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-oem-tools-4.15.0-1103",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-tools-4.15.0-1103-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "linux-udebs-oem",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "md-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "message-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "mouse-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "multipath-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nfs-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-shared-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "nic-usb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "parport-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pata-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pcmcia-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "plip-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "ppp-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "sata-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "scsi-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "serial-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "storage-core-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "usb-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "virtio-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
},
{
"binary_name": "vlan-modules-4.15.0-1103-oem-di",
"binary_version": "4.15.0-1103.114"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-headers-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-image-unsigned-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-modules-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-modules-extra-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-oracle-5.0-headers-5.0.0-1014",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-oracle-5.0-tools-5.0.0-1014",
"binary_version": "5.0.0-1014.19"
},
{
"binary_name": "linux-tools-5.0.0-1014-oracle",
"binary_version": "5.0.0-1014.19"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-headers-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-modules-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-oracle-5.3-headers-5.3.0-1030",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-oracle-5.3-tools-5.3.0-1030",
"binary_version": "5.3.0-1030.32~18.04.1"
},
{
"binary_name": "linux-tools-5.3.0-1030-oracle",
"binary_version": "5.3.0-1030.32~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "block-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "block-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "crypto-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "crypto-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "dasd-extra-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "dasd-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "fat-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "fat-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "fb-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "firewire-core-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "floppy-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "fs-core-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "fs-core-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "fs-secondary-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "fs-secondary-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "input-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "input-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "ipmi-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "ipmi-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "kernel-image-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "kernel-image-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-buildinfo-5.4.0-195-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-buildinfo-5.4.0-195-generic-lpae",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-buildinfo-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-cloud-tools-5.4.0-195",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-cloud-tools-5.4.0-195-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-cloud-tools-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-headers-5.4.0-195",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-headers-5.4.0-195-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-headers-5.4.0-195-generic-lpae",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-headers-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-image-5.4.0-195-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-image-5.4.0-195-generic-lpae",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-image-unsigned-5.4.0-195-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-image-unsigned-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-modules-5.4.0-195-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-modules-5.4.0-195-generic-lpae",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-modules-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-modules-extra-5.4.0-195-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-source-5.4.0",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-tools-5.4.0-195",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-tools-5.4.0-195-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-tools-5.4.0-195-generic-lpae",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-tools-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-tools-common",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-tools-host",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "linux-udebs-generic-lpae",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "md-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "md-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "message-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "mouse-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "mouse-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "multipath-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "multipath-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nfs-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nfs-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nic-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nic-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nic-pcmcia-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nic-shared-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nic-shared-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nic-usb-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "nic-usb-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "parport-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "parport-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "pata-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "pcmcia-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "pcmcia-storage-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "plip-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "plip-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "ppp-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "ppp-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "sata-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "sata-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "scsi-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "scsi-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "serial-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "storage-core-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "storage-core-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "usb-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "usb-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "virtio-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "vlan-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215"
},
{
"binary_name": "vlan-modules-5.4.0-195-generic-lpae-di",
"binary_version": "5.4.0-195.215"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-5.4.0-1132",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-aws-headers-5.4.0-1132",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-aws-tools-5.4.0-1132",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-buildinfo-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-headers-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-modules-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-modules-extra-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142"
},
{
"binary_name": "linux-tools-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-5.15-cloud-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-aws-5.15-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-aws-5.15-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.4.0-1137",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-azure-headers-5.4.0-1137",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-azure-tools-5.4.0-1137",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-buildinfo-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-headers-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-modules-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-modules-extra-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144"
},
{
"binary_name": "linux-tools-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-5.15-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-azure-5.15-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-azure-5.15-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-bluefield-headers-5.4.0-1092",
"binary_version": "5.4.0-1092.99"
},
{
"binary_name": "linux-bluefield-tools-5.4.0-1092",
"binary_version": "5.4.0-1092.99"
},
{
"binary_name": "linux-buildinfo-5.4.0-1092-bluefield",
"binary_version": "5.4.0-1092.99"
},
{
"binary_name": "linux-headers-5.4.0-1092-bluefield",
"binary_version": "5.4.0-1092.99"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1092-bluefield",
"binary_version": "5.4.0-1092.99"
},
{
"binary_name": "linux-modules-5.4.0-1092-bluefield",
"binary_version": "5.4.0-1092.99"
},
{
"binary_name": "linux-tools-5.4.0-1092-bluefield",
"binary_version": "5.4.0-1092.99"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145"
},
{
"binary_name": "linux-gcp-headers-5.4.0-1136",
"binary_version": "5.4.0-1136.145"
},
{
"binary_name": "linux-gcp-tools-5.4.0-1136",
"binary_version": "5.4.0-1136.145"
},
{
"binary_name": "linux-headers-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145"
},
{
"binary_name": "linux-modules-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145"
},
{
"binary_name": "linux-modules-extra-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145"
},
{
"binary_name": "linux-tools-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-gcp-5.15-headers-5.15.0-1068",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-gcp-5.15-tools-5.15.0-1068",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1099-gkeop",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1099-gkeop",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-gkeop-cloud-tools-5.4.0-1099",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-gkeop-headers-5.4.0-1099",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-gkeop-source-5.4.0",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-gkeop-tools-5.4.0-1099",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-headers-5.4.0-1099-gkeop",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1099-gkeop",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-modules-5.4.0-1099-gkeop",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-modules-extra-5.4.0-1099-gkeop",
"binary_version": "5.4.0-1099.103"
},
{
"binary_name": "linux-tools-5.4.0-1099-gkeop",
"binary_version": "5.4.0-1099.103"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-cloud-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-headers-5.15.0-1052",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-gkeop-5.15-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-cloud-tools-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-cloud-tools-common",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-headers-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-source-5.15.0",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-common",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-hwe-5.15-tools-host",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-generic",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-headers-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-ibm-headers-5.4.0-1079",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-ibm-source-5.4.0",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-ibm-tools-5.4.0-1079",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-ibm-tools-common",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-modules-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-modules-extra-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84"
},
{
"binary_name": "linux-tools-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-headers-5.15.0-1062",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-source-5.15.0",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-ibm-5.15-tools-5.15.0-1062",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-cloud-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-cloud-tools-common",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-headers-5.15.0-1064",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-common",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-intel-iotg-5.15-tools-host",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1043-iot",
"binary_version": "5.4.0-1043.44"
},
{
"binary_name": "linux-headers-5.4.0-1043-iot",
"binary_version": "5.4.0-1043.44"
},
{
"binary_name": "linux-image-5.4.0-1043-iot",
"binary_version": "5.4.0-1043.44"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1043-iot",
"binary_version": "5.4.0-1043.44"
},
{
"binary_name": "linux-iot-headers-5.4.0-1043",
"binary_version": "5.4.0-1043.44"
},
{
"binary_name": "linux-iot-tools-5.4.0-1043",
"binary_version": "5.4.0-1043.44"
},
{
"binary_name": "linux-iot-tools-common",
"binary_version": "5.4.0-1043.44"
},
{
"binary_name": "linux-modules-5.4.0-1043-iot",
"binary_version": "5.4.0-1043.44"
},
{
"binary_name": "linux-tools-5.4.0-1043-iot",
"binary_version": "5.4.0-1043.44"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1120-kvm",
"binary_version": "5.4.0-1120.128"
},
{
"binary_name": "linux-headers-5.4.0-1120-kvm",
"binary_version": "5.4.0-1120.128"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1120-kvm",
"binary_version": "5.4.0-1120.128"
},
{
"binary_name": "linux-kvm-headers-5.4.0-1120",
"binary_version": "5.4.0-1120.128"
},
{
"binary_name": "linux-kvm-tools-5.4.0-1120",
"binary_version": "5.4.0-1120.128"
},
{
"binary_name": "linux-modules-5.4.0-1120-kvm",
"binary_version": "5.4.0-1120.128"
},
{
"binary_name": "linux-tools-5.4.0-1120-kvm",
"binary_version": "5.4.0-1120.128"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-cloud-tools-common",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-headers-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-5.15.0-121",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-common",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-5.15-tools-host",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-nvidia-tegra-5.15-headers-5.15.0-1030",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-nvidia-tegra-5.15-tools-5.15.0-1030",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1030-nvidia-tegra",
"binary_version": "5.15.0-1030.30~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1030-nvidia-tegra-rt",
"binary_version": "5.15.0-1030.30~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140"
},
{
"binary_name": "linux-headers-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140"
},
{
"binary_name": "linux-modules-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140"
},
{
"binary_name": "linux-modules-extra-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140"
},
{
"binary_name": "linux-oracle-headers-5.4.0-1131",
"binary_version": "5.4.0-1131.140"
},
{
"binary_name": "linux-oracle-tools-5.4.0-1131",
"binary_version": "5.4.0-1131.140"
},
{
"binary_name": "linux-tools-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-oracle-5.15-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-oracle-5.15-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128"
},
{
"binary_name": "linux-headers-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128"
},
{
"binary_name": "linux-image-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128"
},
{
"binary_name": "linux-modules-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128"
},
{
"binary_name": "linux-raspi-headers-5.4.0-1116",
"binary_version": "5.4.0-1116.128"
},
{
"binary_name": "linux-raspi-tools-5.4.0-1116",
"binary_version": "5.4.0-1116.128"
},
{
"binary_name": "linux-tools-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-image-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-riscv-5.15-headers-5.15.0-1065",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-riscv-5.15-tools-5.15.0-1065",
"binary_version": "5.15.0-1065.69~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1065-generic",
"binary_version": "5.15.0-1065.69~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1051-xilinx-zynqmp",
"binary_version": "5.4.0-1051.55"
},
{
"binary_name": "linux-headers-5.4.0-1051-xilinx-zynqmp",
"binary_version": "5.4.0-1051.55"
},
{
"binary_name": "linux-image-5.4.0-1051-xilinx-zynqmp",
"binary_version": "5.4.0-1051.55"
},
{
"binary_name": "linux-modules-5.4.0-1051-xilinx-zynqmp",
"binary_version": "5.4.0-1051.55"
},
{
"binary_name": "linux-tools-5.4.0-1051-xilinx-zynqmp",
"binary_version": "5.4.0-1051.55"
},
{
"binary_name": "linux-xilinx-zynqmp-headers-5.4.0-1051",
"binary_version": "5.4.0-1051.55"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-5.4.0-1051",
"binary_version": "5.4.0-1051.55"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-5.11-cloud-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-aws-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-aws-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-1028-aws",
"binary_version": "5.11.0-1028.31~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-5.13-cloud-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-aws-5.13-headers-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-aws-5.13-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1031-aws",
"binary_version": "5.13.0-1031.35~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-5.8-cloud-tools-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-aws-5.8-headers-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-aws-5.8-tools-5.8.0-1042",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1042-aws",
"binary_version": "5.8.0-1042.44~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-5.11-cloud-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-azure-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-azure-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-buildinfo-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-cloud-tools-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-headers-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-modules-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
},
{
"binary_name": "linux-tools-5.11.0-1028-azure",
"binary_version": "5.11.0-1028.31~20.04.2"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-5.13-cloud-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-azure-5.13-headers-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-azure-5.13-tools-5.13.0-1031",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1031-azure",
"binary_version": "5.13.0-1031.37~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-5.8-cloud-tools-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-azure-5.8-headers-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-azure-5.8-tools-5.8.0-1043",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1043-azure",
"binary_version": "5.8.0-1043.46~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-image-unsigned-5.4.0-1103-azure-fde",
"binary_version": "5.4.0-1103.109+cvm1.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-gcp-5.11-headers-5.11.0-1029",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-gcp-5.11-tools-5.11.0-1029",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-headers-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-modules-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-modules-extra-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
},
{
"binary_name": "linux-tools-5.11.0-1029-gcp",
"binary_version": "5.11.0-1029.33~20.04.3"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-gcp-5.13-headers-5.13.0-1033",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-gcp-5.13-tools-5.13.0-1033",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1033-gcp",
"binary_version": "5.13.0-1033.40~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-gcp-5.8-headers-5.8.0-1039",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-gcp-5.8-tools-5.8.0-1039",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-headers-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-modules-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-modules-extra-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
},
{
"binary_name": "linux-tools-5.8.0-1039-gcp",
"binary_version": "5.8.0-1039.41"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-gke-headers-5.4.0-1105",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-gke-tools-5.4.0-1105",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-headers-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-modules-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-modules-extra-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
},
{
"binary_name": "linux-tools-5.4.0-1105-gke",
"binary_version": "5.4.0-1105.112"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-gke-5.15-headers-5.15.0-1039",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-gke-5.15-tools-5.15.0-1039",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-headers-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
},
{
"binary_name": "linux-tools-5.15.0-1039-gke",
"binary_version": "5.15.0-1039.44~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "block-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "block-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "block-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "crypto-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "dasd-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fat-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "floppy-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-core-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "input-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ipmi-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "kernel-image-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-cloud-tools-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-cloud-tools-common",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-headers-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-source-5.11.0",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-5.11.0-46",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-common",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-tools-host",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-hwe-5.11-udebs-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic-64k",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-generic-lpae",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-46-lowlatency",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "md-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "message-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "message-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "mouse-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "multipath-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nfs-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "parport-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pata-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "plip-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "ppp-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "sata-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "scsi-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "serial-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "storage-core-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "usb-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "virtio-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "virtio-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-64k-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-di",
"binary_version": "5.11.0-46.51~20.04.1"
},
{
"binary_name": "vlan-modules-5.11.0-46-generic-lpae-di",
"binary_version": "5.11.0-46.51~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "block-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "block-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "block-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "crypto-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "dasd-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fat-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "floppy-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-core-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "input-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ipmi-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "kernel-image-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-cloud-tools-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-cloud-tools-common",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-headers-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-source-5.13.0",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-5.13.0-52",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-common",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-tools-host",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-hwe-5.13-udebs-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic-64k",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-generic-lpae",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-52-lowlatency",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "md-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "message-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "message-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "mouse-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "multipath-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nfs-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "parport-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pata-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "plip-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "ppp-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "sata-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "scsi-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "serial-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "storage-core-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "usb-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "virtio-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "virtio-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-64k-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-di",
"binary_version": "5.13.0-52.59~20.04.1"
},
{
"binary_name": "vlan-modules-5.13.0-52-generic-lpae-di",
"binary_version": "5.13.0-52.59~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "block-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "block-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "block-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "dasd-extra-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "dasd-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "floppy-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-cloud-tools-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-cloud-tools-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-cloud-tools-common",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-headers-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-source-5.8.0",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-5.8.0-63",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-common",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-tools-host",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-hwe-5.8-udebs-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic-64k",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-generic-lpae",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-63-lowlatency",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pata-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pcmcia-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "serial-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-64k-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-di",
"binary_version": "5.8.0-63.71~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-63-generic-lpae-di",
"binary_version": "5.8.0-63.71~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-cloud-tools-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-headers-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-cloud-tools-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-cloud-tools-common",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-headers-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-source-5.13.0",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-5.13.0-1017",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-common",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-intel-5.13-tools-host",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-modules-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-modules-extra-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
},
{
"binary_name": "linux-tools-5.13.0-1017-intel",
"binary_version": "5.13.0-1017.19"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-headers-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-image-unsigned-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-modules-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-headers-5.10.0-1057",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-tools-5.10.0-1057",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-oem-5.10-tools-host",
"binary_version": "5.10.0-1057.61"
},
{
"binary_name": "linux-tools-5.10.0-1057-oem",
"binary_version": "5.10.0-1057.61"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-headers-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-modules-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-headers-5.13.0-1029",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-tools-5.13.0-1029",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-oem-5.13-tools-host",
"binary_version": "5.13.0-1029.36"
},
{
"binary_name": "linux-tools-5.13.0-1029-oem",
"binary_version": "5.13.0-1029.36"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-headers-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-image-unsigned-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-modules-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-modules-iwlwifi-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-headers-5.14.0-1059",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-tools-5.14.0-1059",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-oem-5.14-tools-host",
"binary_version": "5.14.0-1059.67"
},
{
"binary_name": "linux-tools-5.14.0-1059-oem",
"binary_version": "5.14.0-1059.67"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-headers-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-image-unsigned-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-modules-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-headers-5.6.0-1056",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-tools-5.6.0-1056",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-oem-5.6-tools-host",
"binary_version": "5.6.0-1056.60"
},
{
"binary_name": "linux-tools-5.6.0-1056-oem",
"binary_version": "5.6.0-1056.60"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-headers-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-oracle-5.11-headers-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-oracle-5.11-tools-5.11.0-1028",
"binary_version": "5.11.0-1028.31~20.04.1"
},
{
"binary_name": "linux-tools-5.11.0-1028-oracle",
"binary_version": "5.11.0-1028.31~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-headers-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-modules-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-oracle-5.13-headers-5.13.0-1036",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-oracle-5.13-tools-5.13.0-1036",
"binary_version": "5.13.0-1036.43~20.04.1"
},
{
"binary_name": "linux-tools-5.13.0-1036-oracle",
"binary_version": "5.13.0-1036.43~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-image-unsigned-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-oracle-5.8-headers-5.8.0-1038",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-oracle-5.8-tools-5.8.0-1038",
"binary_version": "5.8.0-1038.39~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-1038-oracle",
"binary_version": "5.8.0-1038.39~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-headers-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-image-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-modules-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-raspi2-headers-5.4.0-1006",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-raspi2-tools-5.4.0-1006",
"binary_version": "5.4.0-1006.6"
},
{
"binary_name": "linux-tools-5.4.0-1006-raspi2",
"binary_version": "5.4.0-1006.6"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "block-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "crypto-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fat-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "firewire-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fs-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "fs-secondary-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "input-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "ipmi-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "kernel-image-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-buildinfo-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-headers-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-image-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-modules-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-modules-extra-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-riscv-headers-5.4.0-40",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-riscv-tools-5.4.0-40",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-tools-5.4.0-40-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "md-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "message-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "mouse-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "multipath-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nfs-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-shared-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "nic-usb-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "parport-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "pata-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "plip-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "ppp-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "sata-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "scsi-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "storage-core-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "usb-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "virtio-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
},
{
"binary_name": "vlan-modules-5.4.0-40-generic-di",
"binary_version": "5.4.0-40.45"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-headers-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-image-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-modules-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-modules-extra-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-riscv-5.11-headers-5.11.0-1031",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-riscv-5.11-tools-5.11.0-1031",
"binary_version": "5.11.0-1031.35"
},
{
"binary_name": "linux-tools-5.11.0-1031-generic",
"binary_version": "5.11.0-1031.35"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "block-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "crypto-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fat-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "firewire-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fs-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "fs-secondary-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "input-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "ipmi-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "kernel-image-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-buildinfo-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-headers-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-image-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-modules-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-modules-extra-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-riscv-5.8-headers-5.8.0-29",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-riscv-5.8-tools-5.8.0-29",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-tools-5.8.0-29-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "md-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "message-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "mouse-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "multipath-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nfs-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-shared-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "nic-usb-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "parport-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "pata-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "plip-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "ppp-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "sata-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "scsi-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "storage-core-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "usb-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "virtio-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
},
{
"binary_name": "vlan-modules-5.8.0-29-generic-di",
"binary_version": "5.8.0-29.31~20.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-extra-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-source-5.15.0",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-generic",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-generic-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-generic-lpae",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-common",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-host",
"binary_version": "5.15.0-121.131"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-allwinner-5.19-headers-5.19.0-1015",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-allwinner-5.19-tools-5.19.0-1015",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-buildinfo-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1015-allwinner",
"binary_version": "5.19.0-1015.15~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-aws-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-aws-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-buildinfo-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-headers-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-modules-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-modules-extra-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
},
{
"binary_name": "linux-tools-5.15.0-1069-aws",
"binary_version": "5.15.0-1069.75"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-5.19-cloud-tools-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-aws-5.19-headers-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-aws-5.19-tools-5.19.0-1029",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-buildinfo-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1029-aws",
"binary_version": "5.19.0-1029.30~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-6.2-cloud-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-aws-6.2-headers-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-aws-6.2-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-aws",
"binary_version": "6.2.0-1018.18~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-6.5-cloud-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-aws-6.5-headers-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-aws-6.5-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1024-aws",
"binary_version": "6.5.0-1024.24~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-6.8-cloud-tools-6.8.0-1016",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-aws-6.8-headers-6.8.0-1016",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-aws-6.8-tools-6.8.0-1016",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-buildinfo-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-headers-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-modules-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-modules-extra-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17~22.04.2"
},
{
"binary_name": "linux-tools-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17~22.04.2"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-azure-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-azure-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-headers-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-modules-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
},
{
"binary_name": "linux-tools-5.15.0-1072-azure",
"binary_version": "5.15.0-1072.81"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-5.19-cloud-tools-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-azure-5.19-headers-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-azure-5.19-tools-5.19.0-1027",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-buildinfo-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-headers-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-modules-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-modules-extra-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
},
{
"binary_name": "linux-tools-5.19.0-1027-azure",
"binary_version": "5.19.0-1027.30~22.04.2"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-6.2-cloud-tools-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-azure-6.2-headers-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-azure-6.2-tools-6.2.0-1019",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1019-azure",
"binary_version": "6.2.0-1019.19~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-6.5-cloud-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-azure-6.5-headers-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-azure-6.5-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1025-azure",
"binary_version": "6.5.0-1025.26~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-6.8-cloud-tools-6.8.0-1015",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-azure-6.8-headers-6.8.0-1015",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-azure-6.8-tools-6.8.0-1015",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-buildinfo-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-headers-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-modules-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-modules-extra-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-modules-involflt-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
},
{
"binary_name": "linux-tools-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17~22.04.2"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-image-unsigned-5.15.0-1072-azure-fde",
"binary_version": "5.15.0-1072.81.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-image-unsigned-5.19.0-1027-azure-fde",
"binary_version": "5.19.0-1027.30~22.04.2.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-image-unsigned-6.2.0-1019-azure-fde",
"binary_version": "6.2.0-1019.19~22.04.1.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-gcp-headers-5.15.0-1068",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-gcp-tools-5.15.0-1068",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-headers-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-modules-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-modules-extra-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
},
{
"binary_name": "linux-tools-5.15.0-1068-gcp",
"binary_version": "5.15.0-1068.76"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-gcp-5.19-headers-5.19.0-1030",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-gcp-5.19-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1030-gcp",
"binary_version": "5.19.0-1030.32~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-gcp-6.2-headers-6.2.0-1021",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-gcp-6.2-tools-6.2.0-1021",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1021-gcp",
"binary_version": "6.2.0-1021.23~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-gcp-6.5-headers-6.5.0-1025",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-gcp-6.5-tools-6.5.0-1025",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1025-gcp",
"binary_version": "6.5.0-1025.27~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17~22.04.1"
},
{
"binary_name": "linux-gcp-6.8-headers-6.8.0-1015",
"binary_version": "6.8.0-1015.17~22.04.1"
},
{
"binary_name": "linux-gcp-6.8-tools-6.8.0-1015",
"binary_version": "6.8.0-1015.17~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-gke-headers-5.15.0-1066",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-gke-tools-5.15.0-1066",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-headers-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-modules-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-modules-extra-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
},
{
"binary_name": "linux-tools-5.15.0-1066-gke",
"binary_version": "5.15.0-1066.72"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-gkeop-cloud-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-gkeop-headers-5.15.0-1052",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-gkeop-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-headers-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-modules-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-modules-extra-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
},
{
"binary_name": "linux-tools-5.15.0-1052-gkeop",
"binary_version": "5.15.0-1052.59"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-buildinfo-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-buildinfo-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-cloud-tools-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-headers-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-cloud-tools-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-cloud-tools-common",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-headers-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-5.19.0-50",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-common",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-hwe-5.19-tools-host",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-unsigned-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-image-unsigned-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-extra-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-ipu6-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-ivsc-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-modules-iwlwifi-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-source-5.19.0",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic-64k",
"binary_version": "5.19.0-50.50"
},
{
"binary_name": "linux-tools-5.19.0-50-generic-lpae",
"binary_version": "5.19.0-50.50"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-cloud-tools-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-cloud-tools-common",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-headers-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-6.2.0-39",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-common",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-hwe-6.2-tools-host",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-source-6.2.0",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic-64k",
"binary_version": "6.2.0-39.40~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-39-generic-lpae",
"binary_version": "6.2.0-39.40~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-cloud-tools-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-cloud-tools-common",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-common",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.5-tools-host",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-source-6.5.0",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic-64k",
"binary_version": "6.5.0-45.45~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-cloud-tools-6.8.0-45",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-headers-6.8.0-45",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-hwe-6.8-tools-6.8.0-45",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-modules-usbio-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-45-generic",
"binary_version": "6.8.0-45.45~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-headers-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-headers-5.15.0-1062",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-source-5.15.0",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-tools-5.15.0-1062",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-ibm-tools-common",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-modules-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-modules-extra-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-tools-5.15.0-1062-ibm",
"binary_version": "5.15.0-1062.65"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-headers-6.8.0-1013",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-source-6.8.0",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-ibm-6.8-tools-6.8.0-1013",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-headers-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-cloud-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-cloud-tools-common",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-headers-5.15.0-1064",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-tools-common",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-intel-iotg-tools-host",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-modules-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-modules-extra-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
},
{
"binary_name": "linux-tools-5.15.0-1064-intel-iotg",
"binary_version": "5.15.0-1064.70"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-headers-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-kvm-headers-5.15.0-1066",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-kvm-tools-5.15.0-1066",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-modules-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
},
{
"binary_name": "linux-tools-5.15.0-1066-kvm",
"binary_version": "5.15.0-1066.71"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-buildinfo-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-cloud-tools-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-headers-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-cloud-tools-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-cloud-tools-common",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-headers-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-tools-5.15.0-121",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-tools-common",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-lowlatency-tools-host",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-lowlatency",
"binary_version": "5.15.0-121.131"
},
{
"binary_name": "linux-tools-5.15.0-121-lowlatency-64k",
"binary_version": "5.15.0-121.131"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-buildinfo-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-cloud-tools-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-headers-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-headers-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-image-unsigned-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-cloud-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-cloud-tools-common",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-headers-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-5.19.0-1030",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-common",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-lowlatency-hwe-5.19-tools-host",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-ipu6-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-ivsc-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-modules-iwlwifi-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-tools-5.19.0-1030-lowlatency",
"binary_version": "5.19.0-1030.30"
},
{
"binary_name": "linux-tools-5.19.0-1030-lowlatency-64k",
"binary_version": "5.19.0-1030.30"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-cloud-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-cloud-tools-common",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-headers-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-6.2.0-1018",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-common",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.2-tools-host",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-ipu6-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-ivsc-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-lowlatency",
"binary_version": "6.2.0-1018.18~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1018-lowlatency-64k",
"binary_version": "6.2.0-1018.18~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-cloud-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-cloud-tools-common",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-lib-rust-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-common",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.5-tools-host",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-lowlatency",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-lowlatency-64k",
"binary_version": "6.5.0-45.45.1~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-cloud-tools-6.8.0-45",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-headers-6.8.0-45",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-lib-rust-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-lowlatency-hwe-6.8-tools-6.8.0-45",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-buildinfo-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-headers-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-headers-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-extra-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-nvidia-fs-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-modules-nvidia-fs-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-cloud-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-cloud-tools-common",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-headers-5.15.0-1064",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-tools-5.15.0-1064",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-tools-common",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-nvidia-tools-host",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-tools-5.15.0-1064-nvidia",
"binary_version": "5.15.0-1064.65"
},
{
"binary_name": "linux-tools-5.15.0-1064-nvidia-lowlatency",
"binary_version": "5.15.0-1064.65"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-buildinfo-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-headers-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-headers-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-image-unsigned-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-extra-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-nvidia-fs-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-modules-nvidia-fs-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-headers-6.2.0-1015",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-tools-6.2.0-1015",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-nvidia-6.2-tools-host",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-tools-6.2.0-1015-nvidia",
"binary_version": "6.2.0-1015.15"
},
{
"binary_name": "linux-tools-6.2.0-1015-nvidia-64k",
"binary_version": "6.2.0-1015.15"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-buildinfo-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-headers-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-headers-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-extra-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-nvidia-fs-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-modules-nvidia-fs-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-headers-6.5.0-1024",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-tools-6.5.0-1024",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-nvidia-6.5-tools-host",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-tools-6.5.0-1024-nvidia",
"binary_version": "6.5.0-1024.25"
},
{
"binary_name": "linux-tools-6.5.0-1024-nvidia-64k",
"binary_version": "6.5.0-1024.25"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-headers-6.8.0-1014",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-nvidia-6.8-tools-6.8.0-1014",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-buildinfo-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-headers-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-headers-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-modules-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-modules-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-modules-extra-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-cloud-tools-common",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-headers-5.15.0-1028",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-tools-5.15.0-1028",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-tools-common",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-nvidia-tegra-tools-host",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-tools-5.15.0-1028-nvidia-tegra",
"binary_version": "5.15.0-1028.28"
},
{
"binary_name": "linux-tools-5.15.0-1028-nvidia-tegra-rt",
"binary_version": "5.15.0-1028.28"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-buildinfo-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-headers-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-headers-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-modules-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-modules-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-modules-extra-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-cloud-tools-common",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-headers-5.15.0-1016",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-tools-5.15.0-1016",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-tools-common",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-nvidia-tegra-igx-tools-host",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-tools-5.15.0-1016-nvidia-tegra-igx",
"binary_version": "5.15.0-1016.16"
},
{
"binary_name": "linux-tools-5.15.0-1016-nvidia-tegra-igx-rt",
"binary_version": "5.15.0-1016.16"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-headers-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-image-unsigned-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-ipu6-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-ivsc-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-modules-iwlwifi-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-headers-5.17.0-1035",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-tools-5.17.0-1035",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-oem-5.17-tools-host",
"binary_version": "5.17.0-1035.36"
},
{
"binary_name": "linux-tools-5.17.0-1035-oem",
"binary_version": "5.17.0-1035.36"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-headers-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-image-unsigned-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-ipu6-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-ivsc-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-modules-iwlwifi-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-headers-6.0.0-1021",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-tools-6.0.0-1021",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-oem-6.0-tools-host",
"binary_version": "6.0.0-1021.21"
},
{
"binary_name": "linux-tools-6.0.0-1021-oem",
"binary_version": "6.0.0-1021.21"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-headers-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-image-unsigned-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-ipu6-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-ivsc-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-modules-iwlwifi-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-headers-6.1.0-1036",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-tools-6.1.0-1036",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-oem-6.1-tools-host",
"binary_version": "6.1.0-1036.36"
},
{
"binary_name": "linux-tools-6.1.0-1036-oem",
"binary_version": "6.1.0-1036.36"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-headers-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-ipu6-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-ivsc-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-iwlwifi-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-modules-usbio-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-headers-6.5.0-1027",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-lib-rust-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-tools-6.5.0-1027",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-oem-6.5-tools-host",
"binary_version": "6.5.0-1027.28"
},
{
"binary_name": "linux-tools-6.5.0-1027-oem",
"binary_version": "6.5.0-1027.28"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-headers-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-modules-extra-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-oracle-headers-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-oracle-tools-5.15.0-1067",
"binary_version": "5.15.0-1067.73"
},
{
"binary_name": "linux-tools-5.15.0-1067-oracle",
"binary_version": "5.15.0-1067.73"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-oracle-6.5-headers-6.5.0-1027",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-oracle-6.5-tools-6.5.0-1027",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1027-oracle",
"binary_version": "6.5.0-1027.27~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1027-oracle-64k",
"binary_version": "6.5.0-1027.27~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-oracle-6.8-headers-6.8.0-1013",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-oracle-6.8-tools-6.8.0-1013",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-headers-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-image-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-modules-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-modules-extra-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-raspi-headers-5.15.0-1062",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-raspi-tools-5.15.0-1062",
"binary_version": "5.15.0-1062.65"
},
{
"binary_name": "linux-tools-5.15.0-1062-raspi",
"binary_version": "5.15.0-1062.65"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-headers-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-modules-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-modules-extra-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-cloud-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-cloud-tools-common",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-headers-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-5.15.0-1032",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-common",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-realtime-tools-host",
"binary_version": "5.15.0-1032.35"
},
{
"binary_name": "linux-tools-5.15.0-1032-realtime",
"binary_version": "5.15.0-1032.35"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-headers-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-image-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-modules-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-modules-extra-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-riscv-headers-5.15.0-1028",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-riscv-tools-5.15.0-1028",
"binary_version": "5.15.0-1028.32"
},
{
"binary_name": "linux-tools-5.15.0-1028-generic",
"binary_version": "5.15.0-1028.32"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-riscv-5.19-headers-5.19.0-1021",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-riscv-5.19-tools-5.19.0-1021",
"binary_version": "5.19.0-1021.23~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1021-generic",
"binary_version": "5.19.0-1021.23~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.5-headers-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.5-tools-6.5.0-45",
"binary_version": "6.5.0-45.45.1~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-45-generic",
"binary_version": "6.5.0-45.45.1~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1~22.04.1"
},
{
"binary_name": "linux-headers-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1~22.04.1"
},
{
"binary_name": "linux-image-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1~22.04.1"
},
{
"binary_name": "linux-modules-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.8-headers-6.8.0-47",
"binary_version": "6.8.0-47.47.1~22.04.1"
},
{
"binary_name": "linux-riscv-6.8-tools-6.8.0-47",
"binary_version": "6.8.0-47.47.1~22.04.1"
},
{
"binary_name": "linux-tools-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-headers-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-image-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-modules-extra-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-starfive-5.19-headers-5.19.0-1020",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-starfive-5.19-tools-5.19.0-1020",
"binary_version": "5.19.0-1020.22~22.04.1"
},
{
"binary_name": "linux-tools-5.19.0-1020-starfive",
"binary_version": "5.19.0-1020.22~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-headers-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-image-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-modules-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-starfive-6.2-headers-6.2.0-1009",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-starfive-6.2-tools-6.2.0-1009",
"binary_version": "6.2.0-1009.10~22.04.1"
},
{
"binary_name": "linux-tools-6.2.0-1009-starfive",
"binary_version": "6.2.0-1009.10~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-headers-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-image-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-modules-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-starfive-6.5-headers-6.5.0-1018",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-starfive-6.5-tools-6.5.0-1018",
"binary_version": "6.5.0-1018.19~22.04.1"
},
{
"binary_name": "linux-tools-6.5.0-1018-starfive",
"binary_version": "6.5.0-1018.19~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-headers-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-image-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-modules-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-tools-5.15.0-1035-xilinx-zynqmp",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-xilinx-zynqmp-headers-5.15.0-1035",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-5.15.0-1035",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-common",
"binary_version": "5.15.0-1035.39"
},
{
"binary_name": "linux-xilinx-zynqmp-tools-host",
"binary_version": "5.15.0-1035.39"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-buildinfo-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-cloud-tools-6.8.0-45",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-cloud-tools-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-headers-6.8.0-45",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-headers-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-headers-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-image-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-image-unsigned-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-image-unsigned-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-lib-rust-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-modules-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-modules-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-modules-extra-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-modules-usbio-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-source-6.8.0",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-tools-6.8.0-45",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-tools-6.8.0-45-generic",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-tools-6.8.0-45-generic-64k",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-tools-common",
"binary_version": "6.8.0-45.45"
},
{
"binary_name": "linux-tools-host",
"binary_version": "6.8.0-45.45"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-6.8.0-1016",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-aws-headers-6.8.0-1016",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-aws-tools-6.8.0-1016",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-buildinfo-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-headers-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-modules-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-modules-extra-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17"
},
{
"binary_name": "linux-tools-6.8.0-1016-aws",
"binary_version": "6.8.0-1016.17"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-6.8.0-1015",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-azure-headers-6.8.0-1015",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-azure-tools-6.8.0-1015",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-buildinfo-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-headers-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-modules-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-modules-extra-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-modules-involflt-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-tools-6.8.0-1015-azure",
"binary_version": "6.8.0-1015.17"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-gcp-headers-6.8.0-1015",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-gcp-tools-6.8.0-1015",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-headers-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-modules-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-modules-extra-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17"
},
{
"binary_name": "linux-tools-6.8.0-1015-gcp",
"binary_version": "6.8.0-1015.17"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1011-gke",
"binary_version": "6.8.0-1011.14"
},
{
"binary_name": "linux-gke-headers-6.8.0-1011",
"binary_version": "6.8.0-1011.14"
},
{
"binary_name": "linux-gke-tools-6.8.0-1011",
"binary_version": "6.8.0-1011.14"
},
{
"binary_name": "linux-headers-6.8.0-1011-gke",
"binary_version": "6.8.0-1011.14"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1011-gke",
"binary_version": "6.8.0-1011.14"
},
{
"binary_name": "linux-modules-6.8.0-1011-gke",
"binary_version": "6.8.0-1011.14"
},
{
"binary_name": "linux-modules-extra-6.8.0-1011-gke",
"binary_version": "6.8.0-1011.14"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1011-gke",
"binary_version": "6.8.0-1011.14"
},
{
"binary_name": "linux-tools-6.8.0-1011-gke",
"binary_version": "6.8.0-1011.14"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-cloud-tools-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-cloud-tools-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-headers-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-gkeop-tools-6.8.0-1002",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-headers-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-modules-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-modules-extra-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
},
{
"binary_name": "linux-tools-6.8.0-1002-gkeop",
"binary_version": "6.8.0-1002.4"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-headers-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-ibm-cloud-tools-common",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-ibm-headers-6.8.0-1013",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-ibm-source-6.8.0",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-ibm-tools-6.8.0-1013",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-extra-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-tools-6.8.0-1013-ibm",
"binary_version": "6.8.0-1013.13"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-cloud-tools-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-headers-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-headers-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-lowlatency-cloud-tools-6.8.0-45",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-lowlatency-cloud-tools-common",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-lowlatency-headers-6.8.0-45",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-lowlatency-lib-rust-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-lowlatency-tools-6.8.0-45",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-lowlatency-tools-common",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-lowlatency-tools-host",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-modules-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-modules-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-tools-6.8.0-45-lowlatency",
"binary_version": "6.8.0-45.45.1"
},
{
"binary_name": "linux-tools-6.8.0-45-lowlatency-64k",
"binary_version": "6.8.0-45.45.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-buildinfo-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-headers-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-headers-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-modules-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-modules-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-modules-extra-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-nvidia-headers-6.8.0-1014",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-nvidia-tools-6.8.0-1014",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-nvidia-tools-host",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-tools-6.8.0-1014-nvidia",
"binary_version": "6.8.0-1014.15"
},
{
"binary_name": "linux-tools-6.8.0-1014-nvidia-64k",
"binary_version": "6.8.0-1014.15"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1014-nvidia-lowlatency",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-buildinfo-6.8.0-1014-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-headers-6.8.0-1014-nvidia-lowlatency",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-headers-6.8.0-1014-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1014-nvidia-lowlatency",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1014-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-modules-6.8.0-1014-nvidia-lowlatency",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-modules-6.8.0-1014-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-modules-extra-6.8.0-1014-nvidia-lowlatency",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1014-nvidia-lowlatency",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-modules-nvidia-fs-6.8.0-1014-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-nvidia-lowlatency-headers-6.8.0-1014",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-nvidia-lowlatency-tools-6.8.0-1014",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-nvidia-lowlatency-tools-host",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-tools-6.8.0-1014-nvidia-lowlatency",
"binary_version": "6.8.0-1014.15.1"
},
{
"binary_name": "linux-tools-6.8.0-1014-nvidia-lowlatency-64k",
"binary_version": "6.8.0-1014.15.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1013-oem",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-headers-6.8.0-1013-oem",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-oem",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-6.8.0-1013-oem",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-1013-oem",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-1013-oem",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-usbio-6.8.0-1013-oem",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-oem-6.8-headers-6.8.0-1013",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-oem-6.8-tools-6.8.0-1013",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-tools-6.8.0-1013-oem",
"binary_version": "6.8.0-1013.13"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-buildinfo-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-headers-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-headers-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-image-unsigned-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-extra-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-modules-extra-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-oracle-headers-6.8.0-1013",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-oracle-tools-6.8.0-1013",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-tools-6.8.0-1013-oracle",
"binary_version": "6.8.0-1013.13"
},
{
"binary_name": "linux-tools-6.8.0-1013-oracle-64k",
"binary_version": "6.8.0-1013.13"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1012-raspi",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-headers-6.8.0-1012-raspi",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-image-6.8.0-1012-raspi",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-modules-6.8.0-1012-raspi",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-raspi-headers-6.8.0-1012",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-raspi-tools-6.8.0-1012",
"binary_version": "6.8.0-1012.13"
},
{
"binary_name": "linux-tools-6.8.0-1012-raspi",
"binary_version": "6.8.0-1012.13"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1"
},
{
"binary_name": "linux-headers-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1"
},
{
"binary_name": "linux-image-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1"
},
{
"binary_name": "linux-modules-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1"
},
{
"binary_name": "linux-riscv-headers-6.8.0-47",
"binary_version": "6.8.0-47.47.1"
},
{
"binary_name": "linux-riscv-tools-6.8.0-47",
"binary_version": "6.8.0-47.47.1"
},
{
"binary_name": "linux-tools-6.8.0-47-generic",
"binary_version": "6.8.0-47.47.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-1009-xilinx",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-headers-6.8.0-1009-xilinx",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-image-6.8.0-1009-xilinx",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-modules-6.8.0-1009-xilinx",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-tools-6.8.0-1009-xilinx",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-xilinx-headers-6.8.0-1009",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-xilinx-tools-6.8.0-1009",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-xilinx-tools-common",
"binary_version": "6.8.0-1009.10"
},
{
"binary_name": "linux-xilinx-tools-host",
"binary_version": "6.8.0-1009.10"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available for NVIDIA BlueField platforms",
"binaries": [
{
"binary_name": "linux-bluefield-cloud-tools-common",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-bluefield-headers-5.15.0-1052",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-bluefield-tools-5.15.0-1052",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-bluefield-tools-host",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-buildinfo-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-headers-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-modules-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-modules-extra-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
},
{
"binary_name": "linux-tools-5.15.0-1052-bluefield",
"binary_version": "5.15.0-1052.54"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-4.15.0-1181",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-azure-headers-4.15.0-1181",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-azure-tools-4.15.0-1181",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~14.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~14.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-headers-4.15.0-1173",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-aws-hwe-cloud-tools-4.15.0-1173",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-aws-hwe-tools-4.15.0-1173",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186~16.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-cloud-tools-4.15.0-1181",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-azure-headers-4.15.0-1181",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-azure-tools-4.15.0-1181",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196~16.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183~16.04.1"
},
{
"binary_name": "linux-gcp-headers-4.15.0-1166",
"binary_version": "4.15.0-1166.183~16.04.1"
},
{
"binary_name": "linux-gcp-tools-4.15.0-1166",
"binary_version": "4.15.0-1166.183~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183~16.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "crypto-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "dasd-extra-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "dasd-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "fat-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "fb-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "firewire-core-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "floppy-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "fs-core-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "fs-secondary-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "input-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "ipmi-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "irda-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "kernel-image-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-229-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-buildinfo-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-229-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-cloud-tools-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-229",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-229-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-hwe-cloud-tools-4.15.0-229",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-hwe-tools-4.15.0-229",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-hwe-udebs-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-image-4.15.0-229-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-229-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-229-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-229-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-source-4.15.0",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-229-generic",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "md-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "message-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "mouse-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "multipath-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "nfs-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "nic-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "nic-shared-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "nic-usb-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "parport-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "pata-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "pcmcia-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "plip-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "ppp-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "sata-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "scsi-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "serial-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "storage-core-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "usb-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "virtio-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
},
{
"binary_name": "vlan-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241~16.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146~16.04.1"
},
{
"binary_name": "linux-headers-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146~16.04.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146~16.04.1"
},
{
"binary_name": "linux-modules-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146~16.04.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146~16.04.1"
},
{
"binary_name": "linux-oracle-headers-4.15.0-1135",
"binary_version": "4.15.0-1135.146~16.04.1"
},
{
"binary_name": "linux-oracle-tools-4.15.0-1135",
"binary_version": "4.15.0-1135.146~16.04.1"
},
{
"binary_name": "linux-tools-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146~16.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "crypto-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "dasd-extra-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "dasd-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "fat-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "fb-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "firewire-core-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "floppy-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "fs-core-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "fs-secondary-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "input-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "ipmi-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "irda-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "kernel-image-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-buildinfo-4.15.0-229-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-buildinfo-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-cloud-tools-4.15.0-229",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-cloud-tools-4.15.0-229-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-cloud-tools-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-cloud-tools-common",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-headers-4.15.0-229",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-headers-4.15.0-229-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-headers-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-image-4.15.0-229-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-image-unsigned-4.15.0-229-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-image-unsigned-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-modules-4.15.0-229-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-modules-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-modules-extra-4.15.0-229-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-source-4.15.0",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-tools-4.15.0-229",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-tools-4.15.0-229-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-tools-4.15.0-229-lowlatency",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-tools-common",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-tools-host",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "linux-udebs-generic",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "md-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "message-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "mouse-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "multipath-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "nfs-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "nic-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "nic-pcmcia-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "nic-shared-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "nic-usb-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "parport-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "pata-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "pcmcia-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "pcmcia-storage-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "plip-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "ppp-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "sata-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "scsi-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "serial-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "storage-core-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "usb-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "virtio-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
},
{
"binary_name": "vlan-modules-4.15.0-229-generic-di",
"binary_version": "4.15.0-229.241"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-cloud-tools-4.15.0-1173",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-aws-headers-4.15.0-1173",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-aws-tools-4.15.0-1173",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-buildinfo-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-headers-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-modules-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-modules-extra-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186"
},
{
"binary_name": "linux-tools-4.15.0-1173-aws",
"binary_version": "4.15.0-1173.186"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-5.4-cloud-tools-5.4.0-1132",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-aws-5.4-headers-5.4.0-1132",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-aws-5.4-tools-5.4.0-1132",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1132-aws",
"binary_version": "5.4.0-1132.142~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-4.15-cloud-tools-4.15.0-1181",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-azure-4.15-headers-4.15.0-1181",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-azure-4.15-tools-4.15.0-1181",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-buildinfo-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-headers-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-modules-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-modules-extra-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196"
},
{
"binary_name": "linux-tools-4.15.0-1181-azure",
"binary_version": "4.15.0-1181.196"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-5.4-cloud-tools-5.4.0-1137",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-azure-5.4-headers-5.4.0-1137",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-azure-5.4-tools-5.4.0-1137",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1137-azure",
"binary_version": "5.4.0-1137.144~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183"
},
{
"binary_name": "linux-gcp-4.15-headers-4.15.0-1166",
"binary_version": "4.15.0-1166.183"
},
{
"binary_name": "linux-gcp-4.15-tools-4.15.0-1166",
"binary_version": "4.15.0-1166.183"
},
{
"binary_name": "linux-headers-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183"
},
{
"binary_name": "linux-modules-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183"
},
{
"binary_name": "linux-modules-extra-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183"
},
{
"binary_name": "linux-tools-4.15.0-1166-gcp",
"binary_version": "4.15.0-1166.183"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145~18.04.1"
},
{
"binary_name": "linux-gcp-5.4-headers-5.4.0-1136",
"binary_version": "5.4.0-1136.145~18.04.1"
},
{
"binary_name": "linux-gcp-5.4-tools-5.4.0-1136",
"binary_version": "5.4.0-1136.145~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1136-gcp",
"binary_version": "5.4.0-1136.145~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "block-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "crypto-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "dasd-extra-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "dasd-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "fat-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "fb-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "firewire-core-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "floppy-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "fs-core-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "fs-secondary-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "input-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "ipmi-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "kernel-image-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-195-generic",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-buildinfo-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-195-generic",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-195-generic",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-cloud-tools-5.4.0-195",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-cloud-tools-common",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-headers-5.4.0-195",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-source-5.4.0",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-tools-5.4.0-195",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-tools-common",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-hwe-5.4-udebs-generic",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-195-generic",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-195-generic",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-195-generic",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-195-generic",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-195-lowlatency",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "md-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "message-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "mouse-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "multipath-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "nfs-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "nic-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "nic-pcmcia-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "nic-shared-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "nic-usb-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "parport-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "pata-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "pcmcia-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "pcmcia-storage-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "plip-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "ppp-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "sata-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "scsi-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "serial-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "storage-core-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "usb-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "virtio-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
},
{
"binary_name": "vlan-modules-5.4.0-195-generic-di",
"binary_version": "5.4.0-195.215~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-cloud-tools-common",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-headers-5.4.0-1079",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-source-5.4.0",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-tools-5.4.0-1079",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-ibm-5.4-tools-common",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1079-ibm",
"binary_version": "5.4.0-1079.84~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1156-kvm",
"binary_version": "4.15.0-1156.161"
},
{
"binary_name": "linux-headers-4.15.0-1156-kvm",
"binary_version": "4.15.0-1156.161"
},
{
"binary_name": "linux-image-4.15.0-1156-kvm",
"binary_version": "4.15.0-1156.161"
},
{
"binary_name": "linux-kvm-headers-4.15.0-1156",
"binary_version": "4.15.0-1156.161"
},
{
"binary_name": "linux-kvm-tools-4.15.0-1156",
"binary_version": "4.15.0-1156.161"
},
{
"binary_name": "linux-modules-4.15.0-1156-kvm",
"binary_version": "4.15.0-1156.161"
},
{
"binary_name": "linux-tools-4.15.0-1156-kvm",
"binary_version": "4.15.0-1156.161"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146"
},
{
"binary_name": "linux-headers-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146"
},
{
"binary_name": "linux-modules-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146"
},
{
"binary_name": "linux-modules-extra-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146"
},
{
"binary_name": "linux-oracle-headers-4.15.0-1135",
"binary_version": "4.15.0-1135.146"
},
{
"binary_name": "linux-oracle-tools-4.15.0-1135",
"binary_version": "4.15.0-1135.146"
},
{
"binary_name": "linux-tools-4.15.0-1135-oracle",
"binary_version": "4.15.0-1135.146"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140~18.04.1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140~18.04.1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140~18.04.1"
},
{
"binary_name": "linux-oracle-5.4-headers-5.4.0-1131",
"binary_version": "5.4.0-1131.140~18.04.1"
},
{
"binary_name": "linux-oracle-5.4-tools-5.4.0-1131",
"binary_version": "5.4.0-1131.140~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1131-oracle",
"binary_version": "5.4.0-1131.140~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro (Infra-only): https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128~18.04.1"
},
{
"binary_name": "linux-headers-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128~18.04.1"
},
{
"binary_name": "linux-image-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128~18.04.1"
},
{
"binary_name": "linux-modules-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128~18.04.1"
},
{
"binary_name": "linux-raspi-5.4-headers-5.4.0-1116",
"binary_version": "5.4.0-1116.128~18.04.1"
},
{
"binary_name": "linux-raspi-5.4-tools-5.4.0-1116",
"binary_version": "5.4.0-1116.128~18.04.1"
},
{
"binary_name": "linux-tools-5.4.0-1116-raspi",
"binary_version": "5.4.0-1116.128~18.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-fips-cloud-tools-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-aws-fips-headers-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.15.0-1051",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1051-aws-fips",
"binary_version": "5.15.0-1051.56+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.15.0-1053",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1053-azure-fips",
"binary_version": "5.15.0-1053.61+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-headers-5.15.0-73",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-tools-5.15.0-73",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-headers-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
},
{
"binary_name": "linux-tools-5.15.0-73-fips",
"binary_version": "5.15.0-73.80+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.15.0-1048",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.15.0-1048",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1048-gcp-fips",
"binary_version": "5.15.0-1048.56+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-fips-headers-4.15.0-2111",
"binary_version": "4.15.0-2111.117"
},
{
"binary_name": "linux-aws-fips-tools-4.15.0-2111",
"binary_version": "4.15.0-2111.117"
},
{
"binary_name": "linux-buildinfo-4.15.0-2111-aws-fips",
"binary_version": "4.15.0-2111.117"
},
{
"binary_name": "linux-headers-4.15.0-2111-aws-fips",
"binary_version": "4.15.0-2111.117"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2111-aws-fips",
"binary_version": "4.15.0-2111.117"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2111-aws-fips",
"binary_version": "4.15.0-2111.117"
},
{
"binary_name": "linux-modules-4.15.0-2111-aws-fips",
"binary_version": "4.15.0-2111.117"
},
{
"binary_name": "linux-modules-extra-4.15.0-2111-aws-fips",
"binary_version": "4.15.0-2111.117"
},
{
"binary_name": "linux-tools-4.15.0-2111-aws-fips",
"binary_version": "4.15.0-2111.117"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-4.15.0-2090",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-azure-fips-headers-4.15.0-2090",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-azure-fips-tools-4.15.0-2090",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-buildinfo-4.15.0-2090-azure-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-cloud-tools-4.15.0-2090-azure-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-headers-4.15.0-2090-azure-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2090-azure-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2090-azure-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-modules-4.15.0-2090-azure-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-modules-extra-4.15.0-2090-azure-fips",
"binary_version": "4.15.0-2090.96"
},
{
"binary_name": "linux-tools-4.15.0-2090-azure-fips",
"binary_version": "4.15.0-2090.96"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-fips-headers-4.15.0-1127",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-fips-tools-4.15.0-1127",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-headers-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-image-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-image-hmac-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-modules-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-modules-extra-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
},
{
"binary_name": "linux-tools-4.15.0-1127-fips",
"binary_version": "4.15.0-1127.138"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-2074-gcp-fips",
"binary_version": "4.15.0-2074.79"
},
{
"binary_name": "linux-gcp-fips-headers-4.15.0-2074",
"binary_version": "4.15.0-2074.79"
},
{
"binary_name": "linux-gcp-fips-tools-4.15.0-2074",
"binary_version": "4.15.0-2074.79"
},
{
"binary_name": "linux-headers-4.15.0-2074-gcp-fips",
"binary_version": "4.15.0-2074.79"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2074-gcp-fips",
"binary_version": "4.15.0-2074.79"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2074-gcp-fips",
"binary_version": "4.15.0-2074.79"
},
{
"binary_name": "linux-modules-4.15.0-2074-gcp-fips",
"binary_version": "4.15.0-2074.79"
},
{
"binary_name": "linux-modules-extra-4.15.0-2074-gcp-fips",
"binary_version": "4.15.0-2074.79"
},
{
"binary_name": "linux-tools-4.15.0-2074-gcp-fips",
"binary_version": "4.15.0-2074.79"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-fips-headers-5.4.0-1132",
"binary_version": "5.4.0-1132.142+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.4.0-1132",
"binary_version": "5.4.0-1132.142+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1132-aws-fips",
"binary_version": "5.4.0-1132.142+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1132-aws-fips",
"binary_version": "5.4.0-1132.142+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1132-aws-fips",
"binary_version": "5.4.0-1132.142+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1132-aws-fips",
"binary_version": "5.4.0-1132.142+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1132-aws-fips",
"binary_version": "5.4.0-1132.142+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1132-aws-fips",
"binary_version": "5.4.0-1132.142+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1132-aws-fips",
"binary_version": "5.4.0-1132.142+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.4.0-1137",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.4.0-1137",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.4.0-1137",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1137-azure-fips",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1137-azure-fips",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1137-azure-fips",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1137-azure-fips",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1137-azure-fips",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1137-azure-fips",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1137-azure-fips",
"binary_version": "5.4.0-1137.144+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1137-azure-fips",
"binary_version": "5.4.0-1137.144+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1106-fips",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-fips-headers-5.4.0-1106",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-fips-tools-5.4.0-1106",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-headers-5.4.0-1106-fips",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1106-fips",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1106-fips",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-modules-5.4.0-1106-fips",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-modules-extra-5.4.0-1106-fips",
"binary_version": "5.4.0-1106.116"
},
{
"binary_name": "linux-tools-5.4.0-1106-fips",
"binary_version": "5.4.0-1106.116"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1136-gcp-fips",
"binary_version": "5.4.0-1136.145+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.4.0-1136",
"binary_version": "5.4.0-1136.145+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.4.0-1136",
"binary_version": "5.4.0-1136.145+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1136-gcp-fips",
"binary_version": "5.4.0-1136.145+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1136-gcp-fips",
"binary_version": "5.4.0-1136.145+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1136-gcp-fips",
"binary_version": "5.4.0-1136.145+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1136-gcp-fips",
"binary_version": "5.4.0-1136.145+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1136-gcp-fips",
"binary_version": "5.4.0-1136.145+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1136-gcp-fips",
"binary_version": "5.4.0-1136.145+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-aws-fips-cloud-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-aws-fips-headers-5.15.0-1069",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-aws-fips-tools-5.15.0-1069",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1069-aws-fips",
"binary_version": "5.15.0-1069.75+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.15.0-1072",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.15.0-1072",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-buildinfo-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-modules-involflt-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1072-azure-fips",
"binary_version": "5.15.0-1072.81+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-fips-headers-5.15.0-121",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-fips-tools-5.15.0-121",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-headers-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-modules-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
},
{
"binary_name": "linux-tools-5.15.0-121-fips",
"binary_version": "5.15.0-121.131+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.15.0-1068",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.15.0-1068",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-headers-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-modules-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-modules-extra-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
},
{
"binary_name": "linux-tools-5.15.0-1068-gcp-fips",
"binary_version": "5.15.0-1068.76+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-headers-6.8.0-78",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-lib-rust-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-fips-tools-6.8.0-78",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-headers-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-hmac-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-unsigned-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-extra-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-ipu6-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-modules-usbio-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
},
{
"binary_name": "linux-tools-6.8.0-78-fips",
"binary_version": "6.8.0-78.78+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-fips-headers-4.15.0-2000",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-aws-fips-tools-4.15.0-2000",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-buildinfo-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-headers-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-image-unsigned-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-modules-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-modules-extra-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
},
{
"binary_name": "linux-tools-4.15.0-2000-aws-fips",
"binary_version": "4.15.0-2000.4"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-azure-fips-headers-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-azure-fips-tools-4.15.0-1002",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-buildinfo-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-cloud-tools-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-headers-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-modules-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-modules-extra-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
},
{
"binary_name": "linux-tools-4.15.0-1002-azure-fips",
"binary_version": "4.15.0-1002.2"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-headers-4.15.0-1011",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-tools-4.15.0-1011",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-headers-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-hmac-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-modules-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-modules-extra-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
},
{
"binary_name": "linux-tools-4.15.0-1011-fips",
"binary_version": "4.15.0-1011.12"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-gcp-fips-headers-4.15.0-1001",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-gcp-fips-tools-4.15.0-1001",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-headers-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-image-unsigned-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-image-unsigned-hmac-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-modules-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-modules-extra-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
},
{
"binary_name": "linux-tools-4.15.0-1001-gcp-fips",
"binary_version": "4.15.0-1001.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-aws-fips-headers-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-aws-fips-tools-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-buildinfo-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-headers-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-modules-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-modules-extra-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
},
{
"binary_name": "linux-tools-5.4.0-1021-aws-fips",
"binary_version": "5.4.0-1021.21+fips2"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-azure-fips-cloud-tools-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-azure-fips-headers-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-azure-fips-tools-5.4.0-1022",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-buildinfo-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-cloud-tools-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1022-azure-fips",
"binary_version": "5.4.0-1022.22+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-headers-5.4.0-1007",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-tools-5.4.0-1007",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-fips-tools-host",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-headers-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-modules-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-modules-extra-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
},
{
"binary_name": "linux-tools-5.4.0-1007-fips",
"binary_version": "5.4.0-1007.8"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"binaries": [
{
"binary_name": "linux-buildinfo-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-gcp-fips-headers-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-gcp-fips-tools-5.4.0-1021",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-headers-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-image-unsigned-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-image-unsigned-hmac-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-modules-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-modules-extra-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
},
{
"binary_name": "linux-tools-5.4.0-1021-gcp-fips",
"binary_version": "5.4.0-1021.21+fips1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-headers-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-cloud-tools-5.15.0-1063",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-cloud-tools-common",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-headers-5.15.0-1063",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-tools-5.15.0-1063",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-tools-common",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-intel-iot-realtime-tools-host",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-modules-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-modules-extra-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
},
{
"binary_name": "linux-tools-5.15.0-1063-intel-iot-realtime",
"binary_version": "5.15.0-1063.65"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-cloud-tools-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-headers-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-image-unsigned-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-modules-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-modules-extra-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-modules-iwlwifi-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-cloud-tools-5.15.0-1070",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-cloud-tools-common",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-headers-5.15.0-1070",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-tools-5.15.0-1070",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-tools-common",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-realtime-tools-host",
"binary_version": "5.15.0-1070.78"
},
{
"binary_name": "linux-tools-5.15.0-1070-realtime",
"binary_version": "5.15.0-1070.78"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-cloud-tools-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-headers-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-image-unsigned-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-modules-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-modules-extra-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-cloud-tools-6.8.1-1009",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-headers-6.8.1-1009",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-realtime-6.8-tools-6.8.1-1009",
"binary_version": "6.8.1-1009.9~22.04.1"
},
{
"binary_name": "linux-tools-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9~22.04.1"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.0-2011-raspi-realtime",
"binary_version": "6.8.0-2011.11"
},
{
"binary_name": "linux-headers-6.8.0-2011-raspi-realtime",
"binary_version": "6.8.0-2011.11"
},
{
"binary_name": "linux-image-6.8.0-2011-raspi-realtime",
"binary_version": "6.8.0-2011.11"
},
{
"binary_name": "linux-modules-6.8.0-2011-raspi-realtime",
"binary_version": "6.8.0-2011.11"
},
{
"binary_name": "linux-raspi-realtime-headers-6.8.0-2011",
"binary_version": "6.8.0-2011.11"
},
{
"binary_name": "linux-raspi-realtime-tools-6.8.0-2011",
"binary_version": "6.8.0-2011.11"
},
{
"binary_name": "linux-tools-6.8.0-2011-raspi-realtime",
"binary_version": "6.8.0-2011.11"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}{
"availability": "Available with Ubuntu Pro: https://ubuntu.com/pro",
"binaries": [
{
"binary_name": "linux-buildinfo-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-cloud-tools-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-headers-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-image-unsigned-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-modules-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-modules-extra-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-modules-iwlwifi-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-realtime-cloud-tools-6.8.1-1009",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-realtime-headers-6.8.1-1009",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-realtime-tools-6.8.1-1009",
"binary_version": "6.8.1-1009.9"
},
{
"binary_name": "linux-tools-6.8.1-1009-realtime",
"binary_version": "6.8.1-1009.9"
}
],
"priority_reason": "The vulnerability depends on the chip->mdios list being empty, which requires either MDIO registration failure (causing driver setup to abort before the vulnerable path is reached) or device teardown racing with PHY operations. Both are kernel-internal conditions the attacker can neither invoke nor influence."
}