Linux
tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields
In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Reject non-stacktrace fields for synthetic stacktrace fields In check_synth_field(), when a synthetic event field is a stacktrace (field->is_stack) and the histogram field is not a "long[" stacktrace array, validation falls through to the generic size and signedness comparison. Because parse_synth_field() sets a stacktrace field's type to "__data_loc unsigned long[]", its size is sizeof(u64) and synth_field_signed() marks it as signed. Consequently, any 8-byte signed scalar histogram field passes the fallback check, and its scalar value is subsequently dereferenced as a kernel stacktrace pointer in get_field_size() and trace_stack(). Furthermore, checking strstr(hist_field->type, "long[") is insufficient because tracepoint fields defined with __bitmask() or __rel_bitmask() also have type "__data_loc unsigned long[]" or "__rel_loc unsigned long[]", whilst create_hist_field() treats them as 4-byte scalar values without HIST_FIELD_FL_STACKTRACE. Propagate HIST_FIELD_FL_STACKTRACE to variable references and field variables (whilst excluding variable aliases from per-element stacktrace capture), and reject any mismatch between HIST_FIELD_FL_STACKTRACE and field->is_stack in check_synth_field().
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= b9453380c1c542fd095a4dbe9251eeba4022bbce, < eba0a6365a0f38f7598a02fc7f9ee341c7efe7f5
- >= 5f52389bdd9eafb63b3a2f804e02aeb17b6a5f55, < 326c45c9e201e3ff4c9e9e0e14c2c91364d6c8be
- >= f3baa42afeea0d5f04ad31525e861199d02210cc, < 6c4e4946febb585d2fc93a02a0cd12cec715bb32
- >= 00cf3d672a9dd409418647e9f98784c339c3ff63, < 7e0d05a6234a984ac23b8a563fb7f66f2572b668
- >= 00cf3d672a9dd409418647e9f98784c339c3ff63, < 648687f2b448d8527cd7b112fe5d4bd0fec85a87
- >= 00cf3d672a9dd409418647e9f98784c339c3ff63, < 1f36e4ddd05d540f363dbaa4c23042549f15b3ef
- >= 00cf3d672a9dd409418647e9f98784c339c3ff63, < deb336ae7c7b341591a6862cf6fcfeca97c77dfd
- >= 00cf3d672a9dd409418647e9f98784c339c3ff63, < a244c241593b5b38a08f0df2cb43c26574efbdcb
- >= 5.10.237, < 5.10.273
- >= 5.15.124, < 5.15.224
- >= 6.1.43, < 6.1.191
Fixed in eba0a6365a0f38f7598a02fc7f9ee341c7efe7f5, 326c45c9e201e3ff4c9e9e0e14c2c91364d6c8be, 6c4e4946febb585d2fc93a02a0cd12cec715bb32, 7e0d05a6234a984ac23b8a563fb7f66f2572b668, 648687f2b448d8527cd7b112fe5d4bd0fec85a87, 1f36e4ddd05d540f363dbaa4c23042549f15b3ef, deb336ae7c7b341591a6862cf6fcfeca97c77dfd, a244c241593b5b38a08f0df2cb43c26574efbdcb, 5.10.273, 5.15.224, 6.1.191
- 6.3
Fixed in 0, 5.10.273, 5.15.224, 6.1.191, 6.6.161, 6.12.115, 6.18.59, 7.2.13, 7.3
Mitigation
Upgrade Linux to eba0a6365a0f38f7598a02fc7f9ee341c7efe7f5 or 326c45c9e201e3ff4c9e9e0e14c2c91364d6c8be or 6c4e4946febb585d2fc93a02a0cd12cec715bb32 or 7e0d05a6234a984ac23b8a563fb7f66f2572b668 or 648687f2b448d8527cd7b112fe5d4bd0fec85a87 or 1f36e4ddd05d540f363dbaa4c23042549f15b3ef or deb336ae7c7b341591a6862cf6fcfeca97c77dfd or a244c241593b5b38a08f0df2cb43c26574efbdcb or 5.10.273 or 5.15.224 or 6.1.191 or later.
Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.161 or 6.12.115 or 6.18.59 or 7.2.13 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.