Answer in brief
CVE-2022-50255 records a High severity (CVSS 7.8) vulnerability in tracing: Fix reading strings from synthetic events. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bd82631d7ccdc894af2738e47abcba2cb6e7dea9 <d9c79fbcbdb6cb10c07c85040eaf615180b26c48 || >=bd82631d7ccdc894af2738e47abcba2cb6e7dea9 <149198d0b884e4606ed1d29b330c70016d878276 || >=bd82631d7ccdc894af2738e47abcba2cb6e7dea9 <f8bae1853196b52ede50950387f5b48cf83b9815 || >=bd82631d7ccdc894af2738e47abcba2cb6e7dea9 <0934ae9977c27133449b6dd8c6213970e7eece38 | d9c79fbcbdb6cb10c07c85040eaf615180b26c48, 149198d0b884e4606ed1d29b330c70016d878276, f8bae1853196b52ede50950387f5b48cf83b9815, 0934ae9977c27133449b6dd8c6213970e7eece38 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-50255 records a High severity (CVSS 7.8) vulnerability in tracing: Fix reading strings from synthetic events. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bd82631d7ccdc894af2738e47abcba2cb6e7dea9 <d9c79fbcbdb6cb10c07c85040eaf615180b26c48 || >=bd82631d7ccdc894af2738e47abcba2cb6e7dea9 <149198d0b884e4606ed1d29b330c70016d878276 || >=bd82631d7ccdc894af2738e47abcba2cb6e7dea9 <f8bae1853196b52ede50950387f5b48cf83b9815 || >=bd82631d7ccdc894af2738e47abcba2cb6e7dea9 <0934ae9977c27133449b6dd8c6213970e7eece38 | d9c79fbcbdb6cb10c07c85040eaf615180b26c48, 149198d0b884e4606ed1d29b330c70016d878276, f8bae1853196b52ede50950387f5b48cf83b9815, 0934ae9977c27133449b6dd8c6213970e7eece38 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Sep 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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
Quoted source text, attributed separately from HOL analysis.