CVE-2022-50255tracing: Fix reading strings from synthetic events
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from bd82631d7ccdc894af2738e47abcba2cb6e7dea9 before d9c79fbcbdb6cb10c07c85040eaf615180b26c48; from bd82631d7ccdc894af2738e47abcba2cb6e7dea9 before 149198d0b884e4606ed1d29b330c70016d878276; from bd82631d7ccdc894af2738e47abcba2cb6e7dea9 before f8bae1853196b52ede50950387f5b48cf83b9815; from bd82631d7ccdc894af2738e47abcba2cb6e7dea9 before 0934ae9977c27133449b6dd8c6213970e7eece38 | CNA record |
linux linux_kernel linux:linux_kernel | from 5.10 before 5.15.75; from 5.16 before 5.19.17; from 6.0 before 6.0.3 | NVD |
References
- https://git.kernel.org/stable/c/d9c79fbcbdb6cb10c07c85040eaf615180b26c48patch
- https://git.kernel.org/stable/c/149198d0b884e4606ed1d29b330c70016d878276patch
- https://git.kernel.org/stable/c/f8bae1853196b52ede50950387f5b48cf83b9815patch
- https://git.kernel.org/stable/c/0934ae9977c27133449b6dd8c6213970e7eece38patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.