{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.18.14-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.18.14-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.18.14-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  net: phy: at803x: fix NULL pointer dereference on AR9331 PHY  Latest kernel will explode on the PHY interrupt config, since it depends now on allocated priv. So, run probe to allocate priv to fix it.   ar9331_switch ethernet.1:10 lan0 (uninitialized): PHY [!ahb!ethernet@1a000000!mdio!switch@10:00] driver [Qualcomm Atheros AR9331 built-in PHY] (irq=13)  CPU 0 Unable to handle kernel paging request at virtual address 0000000a, epc == 8050e8a8, ra == 80504b34          ...  Call Trace:  [\u003c8050e8a8\u003e] at803x_config_intr+0x5c/0xd0  [\u003c80504b34\u003e] phy_request_interrupt+0xa8/0xd0  [\u003c8050289c\u003e] phylink_bringup_phy+0x2d8/0x3ac  [\u003c80502b68\u003e] phylink_fwnode_phy_connect+0x118/0x130  [\u003c8074d8ec\u003e] dsa_slave_create+0x270/0x420  [\u003c80743b04\u003e] dsa_port_setup+0x12c/0x148  [\u003c8074580c\u003e] dsa_register_switch+0xaf0/0xcc0  [\u003c80511344\u003e] ar9331_sw_probe+0x370/0x388  [\u003c8050cb78\u003e] mdio_probe+0x44/0x70  [\u003c804df300\u003e] really_probe+0x200/0x424  [\u003c804df7b4\u003e] __driver_probe_device+0x290/0x298  [\u003c804df810\u003e] driver_probe_device+0x54/0xe4  [\u003c804dfd50\u003e] __device_attach_driver+0xe4/0x130  [\u003c804dcb00\u003e] bus_for_each_drv+0xb4/0xd8  [\u003c804dfac4\u003e] __device_attach+0x104/0x1a4  [\u003c804ddd24\u003e] bus_probe_device+0x48/0xc4  [\u003c804deb44\u003e] deferred_probe_work_func+0xf0/0x10c  [\u003c800a0ffc\u003e] process_one_work+0x314/0x4d4  [\u003c800a17fc\u003e] worker_thread+0x2a4/0x354  [\u003c800a9a54\u003e] kthread+0x134/0x13c  [\u003c8006306c\u003e] ret_from_kernel_thread+0x14/0x1c  Same Issue would affect some other PHYs (QCA8081, QCA9561), so fix it too.",
  "id": "DEBIAN-CVE-2022-49692",
  "modified": "2026-09-01T19:48:03.253313046Z",
  "published": "2025-02-26T07:01:43.990Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2022-49692"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2022-49692"
  ]
}