Review reviewHigh

CVE-2022-50255

Linux Linux, linux kernel

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...

CVSS
7.1
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.09.15
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.1

Vulnerability overview

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...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= bd82631d7ccdc894af2738e47abcba2cb6e7dea9 < d9c79fbcbdb6cb10c07c85040eaf615180b26c48, >= bd82631d7ccdc894af2738e47abcba2cb6e7dea9 < 149198d0b884e4606ed1d29b330c70016d878276, >= bd82631d7ccdc894af2738e47abcba2cb6e7dea9 < f8bae1853196b52ede50950387f5b48cf83b9815, >= bd82631d7ccdc894af2738e47abcba2cb6e7dea9 < 0934ae9977c27133449b6dd8c6213970e7eece38, >= 5.10, >= 5.10 < 5.15.75, >= 5.16 < 5.19.17, >= 6.0 < 6.0.3
Fixed versions
5.15.75, 5.19.17, 6.0.3

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CWE
CWE-125