{
  "cveId": "CVE-2022-49613",
  "url": "https://patchblox.com/security/cve/CVE-2022-49613",
  "summary": "CVE-2022-49613 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49613, released February 26, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  serial: 8250: Fix PM usage_count for console han...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  serial: 8250: Fix PM usage_count for console handover  When console is enabled, univ8250_console_setup() calls serial8250_console_setup() before .dev is set to uart_port. Therefore, it will not call pm_runtime_get_sync(). Later, when the actual driver is going to take over univ8250_console_exit() is called. As .dev is already set, serial8250_console_exit() makes pm_runtime_put_sync() call with usage count being zero triggering PM usage count warning (extra debug for univ8250_console_setup(), univ8250_console_exit(), and serial8250_register_ports()):  [    0.068987] univ8250_console_setup ttyS0 nodev [    0.499670] printk: console [ttyS0] enabled [    0.717955] printk: console [ttyS0] printing thread started [    1.960163] serial8250_register_ports assigned dev for ttyS0 [    1.976830] printk: console [ttyS0] disabled [    1.976888] printk: console [ttyS0] printing thread stopped [    1.977073] univ8250_console_exit ttyS0 usage:0 [    1.977075] serial8250 serial8250: Runtime PM usage count underflow! [    1.977429] dw-apb-uart.6: ttyS0 at MMIO 0x4010006000 (irq = 33, base_baud = 115200) is a 16550A [    1.977812] univ8250_console_setup ttyS0 usage:2 [    1.978167] printk: console [ttyS0] printing thread started [    1.978203] printk: console [ttyS0] enabled  To fix the issue, call pm_runtime_get_sync() in serial8250_register_ports() as soon as .dev is set for an uart_port if it has console enabled.  This problem became apparent only recently because 82586a721595 (\u0022PM: runtime: Avoid device usage count underflows\u0022) added the warning printout. I confirmed this problem also occurs with v5.18 (w/o the warning printout, obviously).",
  "published": "2025-02-26T07:01:36Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00261,
  "epssPercentile": 0.17953,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.18.14-1",
      "fix": "DEBIAN-CVE-2022-49613",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49613",
      "released": "2025-02-26T07:01:36Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.18.14-1",
      "fix": "DEBIAN-CVE-2022-49613",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49613",
      "released": "2025-02-26T07:01:36Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.18.14-1",
      "fix": "DEBIAN-CVE-2022-49613",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49613",
      "released": "2025-02-26T07:01:36Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}