CVE-2022-50255
tracing: Fix reading strings from synthetic events
- Published
- Updated
- Reserved
- Assigned by
- Linux
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
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Weakness
Affected products
- affected bd82631d7ccdc894af2738e47abcba2cb6e7dea9 – < d9c79fbcbdb6cb10c07c85040eaf615180b26c48
- affected bd82631d7ccdc894af2738e47abcba2cb6e7dea9 – < 149198d0b884e4606ed1d29b330c70016d878276
- affected bd82631d7ccdc894af2738e47abcba2cb6e7dea9 – < f8bae1853196b52ede50950387f5b48cf83b9815
- affected bd82631d7ccdc894af2738e47abcba2cb6e7dea9 – < 0934ae9977c27133449b6dd8c6213970e7eece38
- affected 5.10
- unaffected < 5.10
- unaffected 5.15.75 – ≤ 5.15.*
- unaffected 5.19.17 – ≤ 5.19.*
- unaffected 6.0.3 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References (4)
- https://git.kernel.org/stable/c/d9c79fbcbdb6cb10c07c85040eaf615180b26c48 (opens in a new tab)
- https://git.kernel.org/stable/c/149198d0b884e4606ed1d29b330c70016d878276 (opens in a new tab)
- https://git.kernel.org/stable/c/f8bae1853196b52ede50950387f5b48cf83b9815 (opens in a new tab)
- https://git.kernel.org/stable/c/0934ae9977c27133449b6dd8c6213970e7eece38 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-50255)Record last updated .