CVE-2024-57930
published 2025-01-21CVE-2024-57930: 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…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
9.8th percentile
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.
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.124-1 (bookworm) | linux 6.1.124-1 (bookworm) |
| debian | linux-6.1 | < linux 6.1.124-1 (bookworm) | linux 6.1.124-1 (bookworm) |
| linux | linux | >= 2f6ad0b613cd45cca48e6eb04f65351db018afb0 < a64e5295ebc4afdefe69cdf16cc286a60ff8ba4b | a64e5295ebc4afdefe69cdf16cc286a60ff8ba4b |
| linux | linux | >= 6.1.122 < 6.1.124 | 6.1.124 |
| linux | linux | >= 6.12.7 < 6.12.9 | 6.12.9 |
| linux | linux | >= 6.6.68 < 6.6.70 | 6.6.70 |
| linux | linux | >= 65a25d9f7ac02e0cf361356e834d1c71d36acca9 < afc6717628f959941d7b33728570568b4af1c4b8 | afc6717628f959941d7b33728570568b4af1c4b8 |
| linux | linux | >= 683eccacc02d2eb25d1c34b8fb0363fcc7e08f64 < 92bd18c74624e5eb9f96e70076aa46293f4b626f | 92bd18c74624e5eb9f96e70076aa46293f4b626f |
| linux | linux | >= 85d7635d54d75a2589f28583dc17feedc3aa4ad6 < 3bcdc9039a6e9e6e47ed689a37b8d57894a3c571 | 3bcdc9039a6e9e6e47ed689a37b8d57894a3c571 |
| linux | linux | >= f3ff759ec636b4094b8eb2c3801e4e6c97a6b712 < 631b1e09e213c86d5a4ce23d45c81af473bb0ac7 | 631b1e09e213c86d5a4ce23d45c81af473bb0ac7 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.124-1 | 6.1.124-1 |
| linux | linux_kernel | >= 0 < 6.12.9-1 | 6.12.9-1 |
| linux | linux_kernel | >= 0 < 6.12.9-1 | 6.12.9-1 |
| linux | linux_kernel | >= 6.1.122 < 6.1.124 | 6.1.124 |
| linux | linux_kernel | >= 6.12.7 < 6.12.9 | 6.12.9 |
| linux | linux_kernel | >= 6.6.68 < 6.6.70 | 6.6.70 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: tracing: Have process_string() also allow arrays
vendor_redhat·2025-01-21·CVSS 5.5
CVE-2024-57930 [MEDIUM] CWE-664 kernel: tracing: Have process_string() also allow arrays
kernel: tracing: Have process_string() also allow arrays
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 de
Debian
CVE-2024-57930: linux - In the Linux kernel, the following vulnerability has been resolved: tracing: Ha...
vendor_debian·2024·CVSS 5.5
CVE-2024-57930 [MEDIUM] CVE-2024-57930: linux - In the Linux kernel, the following vulnerability has been resolved: tracing: Ha...
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", __
OSV
CVE-2024-57930: In the Linux kernel, the following vulnerability has been resolved: tracing: Have process_string() also allow arrays In order to catch a common bug wh
osv·2025-01-21·CVSS 5.5
CVE-2024-57930 [MEDIUM] CVE-2024-57930: In the Linux kernel, the following vulnerability has been resolved: tracing: Have process_string() also allow arrays In order to catch a common bug wh
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", __
GHSA
GHSA-j6wf-6qh3-cm45: In the Linux kernel, the following vulnerability has been resolved:
tracing: Have process_string() also allow arrays
In order to catch a common bug
ghsa_unreviewed·2025-01-21
CVE-2024-57930 [MEDIUM] GHSA-j6wf-6qh3-cm45: In the Linux kernel, the following vulnerability has been resolved:
tracing: Have process_string() also allow arrays
In order to catch a common bug
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
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/3bcdc9039a6e9e6e47ed689a37b8d57894a3c571https://git.kernel.org/stable/c/631b1e09e213c86d5a4ce23d45c81af473bb0ac7https://git.kernel.org/stable/c/92bd18c74624e5eb9f96e70076aa46293f4b626fhttps://git.kernel.org/stable/c/a64e5295ebc4afdefe69cdf16cc286a60ff8ba4bhttps://git.kernel.org/stable/c/afc6717628f959941d7b33728570568b4af1c4b8https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
2025-01-21
Published