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 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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.124, 6.12.9, 6.6.70
- CVEs
- CVE-2024-57930
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 11:26 UTC · Revision 1
Source evidence
tracing: Have process_string() also allow arrays
core-osv · Original sourcePublished 21 Jan 2025, 12:01 UTC
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.
osv:CVE-2024-57930
Kernel
Fixed versions: 6.1.124, 6.6.70, 6.12.9
Complete source record
{
"id": "8f082794a402ee9c8a0c42d42e2588df8564bfa5ebf6a3aac35a283b8885efda",
"url": "https://osv.dev/vulnerability/CVE-2024-57930",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "tracing: Have process_string() also allow arrays",
"summary": "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.",
"evidence": "osv:CVE-2024-57930",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.124",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.70",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2024-57930",
"aliases": [
"CVE-2024-57930"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "85d7635d54d75a2589f28583dc17feedc3aa4ad6"
},
{
"fixed": "3bcdc9039a6e9e6e47ed689a37b8d57894a3c571"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "f3ff759ec636b4094b8eb2c3801e4e6c97a6b712"
},
{
"fixed": "631b1e09e213c86d5a4ce23d45c81af473bb0ac7"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2f6ad0b613cd45cca48e6eb04f65351db018afb0"
},
{
"fixed": "a64e5295ebc4afdefe69cdf16cc286a60ff8ba4b"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "683eccacc02d2eb25d1c34b8fb0363fcc7e08f64"
},
{
"fixed": "92bd18c74624e5eb9f96e70076aa46293f4b626f"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "65a25d9f7ac02e0cf361356e834d1c71d36acca9"
},
{
"fixed": "afc6717628f959941d7b33728570568b4af1c4b8"
}
]
}
],
"versions": [
"v6.1.123",
"v6.1.122",
"v6.6.69",
"v6.6.68",
"v6.12.8",
"v6.12.7"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-57930.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.1.122"
},
{
"fixed": "6.1.124"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.6.68"
},
{
"fixed": "6.6.70"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.12.7"
},
{
"fixed": "6.12.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-57930.json"
}
}
],
"modified": "2026-10-28T02:30:51.007099004Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/3bcdc9039a6e9e6e47ed689a37b8d57894a3c571",
"https://git.kernel.org/stable/c/631b1e09e213c86d5a4ce23d45c81af473bb0ac7",
"https://git.kernel.org/stable/c/92bd18c74624e5eb9f96e70076aa46293f4b626f",
"https://git.kernel.org/stable/c/a64e5295ebc4afdefe69cdf16cc286a60ff8ba4b",
"https://git.kernel.org/stable/c/afc6717628f959941d7b33728570568b4af1c4b8",
"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/57xxx/CVE-2024-57930.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-57930",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/57xxx/CVE-2024-57930.json"
}
},
"related_cves": [
{
"value": "CVE-2024-57930",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 519130,
"published_at": "2025-01-21T12:01:27.807+00:00"
}