{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-42224",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-42224"
  ],
  "published": "2024-07-30T07:47:52Z",
  "summary": "net: dsa: mv88e6xxx: Correct check for empty list",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: mv88e6xxx: Correct check for empty list\n\nSince commit a3c53be55c95 (\"net: dsa: mv88e6xxx: Support multiple MDIO\nbusses\") mv88e6xxx_default_mdio_bus() has checked that the\nreturn value of list_first_entry() is non-NULL.\n\nThis appears to be intended to guard against the list chip->mdios being\nempty.  However, it is not the correct check as the implementation of\nlist_first_entry is not designed to return NULL for empty lists.\n\nInstead, use list_first_entry_or_null() which does return NULL if the\nlist is empty.\n\nFlagged by Smatch.\nCompile tested only.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.98",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-42224"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/47d28dde172696031c880c5778633cdca30394ee"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3bf8d70e1455f87856640c3433b3660a31001618"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2a2fe25a103cef73cde356e6d09da10f607e93f5"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8c2c3cca816d074c75a2801d1ca0dea7b0148114"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/aa03f591ef31ba603a4a99d05d25a0f21ab1cd89"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3f25b5f1635449036692a44b771f39f772190c1d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f75625db838ade28f032dacd0f0c8baca42ecde4"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4c7f3950a9fd53a62b156c0fe7c3a2c43b0ba19b"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:52:36Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.0,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The only entry points are driver probe/`mv88e6xxx_setup()` on a DT-described Marvell DSA switch and local netdev management paths (ifup, ethtool/PHY and SERDES register access) that funnel into `mv88e6xxx_phy_read/write*()` and the PCS init routines; no received packet or remote peer data reaches `mv88e6xxx_default_mdio_bus()`.\nAC:H - The flaw only manifests when `chip->mdios` is empty, but `mv88e6xxx_mdios_register()` unconditionally registers the internal MDIO bus and aborts setup on failure, and `mv88e6xxx_mdios_unregister()` never `list_del`s entries, so the empty-list state is an internal driver condition an attacker cannot create or influence by any sequence of actions.\nPR:L - Post-boot the affected helpers are driven from the DSA user port's MDIO/PHY and SERDES read paths, which a local unprivileged account with access to the switch netdev can exercise; no CAP_NET_ADMIN or root is needed to reach the read side.\nUI:N - The affected paths run automatically during driver probe, port setup and link bring-up, and the PHY/SERDES reads can be driven by the attacker's own process; no victim action is required.\nS:U - The bogus pointer, its dereference and any resulting corruption stay entirely within the kernel's own security authority, with no VM, IOMMU or sandbox boundary crossed.\nC:H - The helper returns `chip->reset` (a `struct gpio_desc *`) reinterpreted as a `struct mii_bus *` \u2014 type confusion that makes the MDIO layer read fields from an unrelated kernel object, and the resulting register values are surfaced back to userspace through the MDIO/PHY read path.\nI:H - The type-confused pointer is written through by `mutex_lock(&bus->mdio_lock)` in `mdiobus_read()`/`mdiobus_write()` and indirect-called via `bus->read`/`bus->write`, giving a memory-corruption and control-flow-hijack primitive rather than a benign NULL dereference.\nA:H - Dereferencing a `gpio_desc` as a `mii_bus` \u2014 taking a mutex at a bogus offset and calling through a non-function-pointer field \u2014 reliably produces a kernel oops or panic, taking the switch and the system down."
    }
  }
}