{
  "cveId": "CVE-2022-50553",
  "url": "https://patchblox.com/security/cve/CVE-2022-50553",
  "summary": "CVE-2022-50553 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50553, released October 7, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  tracing/hist: Fix out-of-bound write on \u0027action_...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  tracing/hist: Fix out-of-bound write on \u0027action_data.var_ref_idx\u0027  When generate a synthetic event with many params and then create a trace action for it [1], kernel panic happened [2].  It is because that in trace_action_create() \u0027data-\u003En_params\u0027 is up to SYNTH_FIELDS_MAX (current value is 64), and array \u0027data-\u003Evar_ref_idx\u0027 keeps indices into array \u0027hist_data-\u003Evar_refs\u0027 for each synthetic event param, but the length of \u0027data-\u003Evar_ref_idx\u0027 is TRACING_MAP_VARS_MAX (current value is 16), so out-of-bound write happened when \u0027data-\u003En_params\u0027 more than 16. In this case, \u0027data-\u003Ematch_data.event\u0027 is overwritten and eventually cause the panic.  To solve the issue, adjust the length of \u0027data-\u003Evar_ref_idx\u0027 to be SYNTH_FIELDS_MAX and add sanity checks to avoid out-of-bound write.  [1]  # cd /sys/kernel/tracing/  # echo \u0022my_synth_event int v1; int v2; int v3; int v4; int v5; int v6;\\ int v7; int v8; int v9; int v10; int v11; int v12; int v13; int v14;\\ int v15; int v16; int v17; int v18; int v19; int v20; int v21; int v22;\\ int v23; int v24; int v25; int v26; int v27; int v28; int v29; int v30;\\ int v31; int v32; int v33; int v34; int v35; int v36; int v37; int v38;\\ int v39; int v40; int v41; int v42; int v43; int v44; int v45; int v46;\\ int v47; int v48; int v49; int v50; int v51; int v52; int v53; int v54;\\ int v55; int v56; int v57; int v58; int v59; int v60; int v61; int v62;\\ int v63\u0022 \u003E\u003E synthetic_events  # echo \u0027hist:keys=pid:ts0=common_timestamp.usecs if comm==\u0022bash\u0022\u0027 \u003E\u003E \\ events/sched/sched_waking/trigger  # echo \u0022hist:keys=next_pid:onmatch(sched.sched_waking).my_synth_event(\\ pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,\\ pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,\\ pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,pid,\\ pid,pid,pid,pid,pid,pid,pid,pid,pid)\u0022 \u003E\u003E events/sched/sched_switch/trigger  [2] BUG: unable to handle page fault for address: ffff91c900000000 PGD 61001067 P4D 61001067 PUD 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 2 PID: 322 Comm: bash Tainted: G        W          6.1.0-rc8\u002B #229 Hardware name: QEMU Standard PC (i440FX \u002B PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 RIP: 0010:strcmp\u002B0xc/0x30 Code: 75 f7 31 d2 44 0f b6 04 16 44 88 04 11 48 83 c2 01 45 84 c0 75 ee c3 cc cc cc cc 0f 1f 00 31 c0 eb 08 48 83 c0 01 84 d2 74 13 \u003C0f\u003E b6 14 07 3a 14 06 74 ef 19 c0 83 c8 01 c3 cc cc cc cc 31 c3 RSP: 0018:ffff9b3b00f53c48 EFLAGS: 00000246 RAX: 0000000000000000 RBX: ffffffffba958a68 RCX: 0000000000000000 RDX: 0000000000000010 RSI: ffff91c943d33a90 RDI: ffff91c900000000 RBP: ffff91c900000000 R08: 00000018d604b529 R09: 0000000000000000 R10: ffff91c9483eddb1 R11: ffff91ca483eddab R12: ffff91c946171580 R13: ffff91c9479f0538 R14: ffff91c9457c2848 R15: ffff91c9479f0538 FS:  00007f1d1cfbe740(0000) GS:ffff91c9bdc80000(0000) knlGS:0000000000000000 CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffff91c900000000 CR3: 0000000006316000 CR4: 00000000000006e0 Call Trace:  \u003CTASK\u003E  __find_event_file\u002B0x55/0x90  action_create\u002B0x76c/0x1060  event_hist_trigger_parse\u002B0x146d/0x2060  ? event_trigger_write\u002B0x31/0xd0  trigger_process_regex\u002B0xbb/0x110  event_trigger_write\u002B0x6b/0xd0  vfs_write\u002B0xc8/0x3e0  ? alloc_fd\u002B0xc0/0x160  ? preempt_count_add\u002B0x4d/0xa0  ? preempt_count_add\u002B0x70/0xa0  ksys_write\u002B0x5f/0xe0  do_syscall_64\u002B0x3b/0x90  entry_SYSCALL_64_after_hwframe\u002B0x63/0xcd RIP: 0033:0x7f1d1d0cf077 Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 \u003C48\u003E 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 RSP: 002b:00007ffcebb0e568 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 0000000000000143 RCX: 00007f1d1d0cf077 RDX: 0000000000000143 RSI: 00005639265aa7e0 RDI: 0000000000000001 RBP: 00005639265aa7e0 R08: 000000000000000a R09: 0000000000000142 R ---truncated---",
  "published": "2025-10-07T16:15:42Z",
  "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.00208,
  "epssPercentile": 0.11034,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.4-1",
      "fix": "DEBIAN-CVE-2022-50553",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50553",
      "released": "2025-10-07T16:15:42Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.1.4-1",
      "fix": "DEBIAN-CVE-2022-50553",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50553",
      "released": "2025-10-07T16:15:42Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.1.4-1",
      "fix": "DEBIAN-CVE-2022-50553",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50553",
      "released": "2025-10-07T16:15:42Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-09T01:18:40Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}