{
  "cveId": "CVE-2022-50255",
  "url": "https://patchblox.com/security/cve/CVE-2022-50255",
  "summary": "CVE-2022-50255 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50255, released September 15, 2025. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix reading strings from synthetic even...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  tracing: Fix reading strings from synthetic events  The follow commands caused a crash:    # cd /sys/kernel/tracing   # echo \u0027s:open char file[]\u0027 \u003E dynamic_events   # echo \u0027hist:keys=common_pid:file=filename:onchange($file).trace(open,$file)\u0027 \u003E events/syscalls/sys_enter_openat/trigger\u0027   # echo 1 \u003E events/synthetic/open/enable  BOOM!  The problem is that the synthetic event field \u0022char file[]\u0022 will read the value given to it as a string without any memory checks to make sure the address is valid. The above example will pass in the user space address and the sythetic event code will happily call strlen() on it and then strscpy() where either one will cause an oops when accessing user space addresses.  Use the helper functions from trace_kprobe and trace_eprobe that can read strings safely (and actually succeed when the address is from user space and the memory is mapped in).  Now the above can show:       packagekitd-1721    [000] ...2.   104.597170: open: file=/usr/lib/rpm/fileattrs/cmake.attr     in:imjournal-978     [006] ...2.   104.599642: open: file=/var/lib/rsyslog/imjournal.state.tmp      packagekitd-1721    [000] ...2.   104.626308: open: file=/usr/lib/rpm/fileattrs/debuginfo.attr",
  "published": "2025-09-15T14:15:36Z",
  "severity": "high",
  "cvss": 7.1,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
  "epss": 0.00168,
  "epssPercentile": 0.06056,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50255",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50255",
      "released": "2025-09-15T14:15:36Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50255",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50255",
      "released": "2025-09-15T14:15:36Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50255",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50255",
      "released": "2025-09-15T14:15:36Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}