VulnerabilityPublished 21 Jan 2025Updated 3 Nov 2025

CVE-2024-57930: Linux kernel · tracing: Have process_string() also allow arrays

Source GCVE Database

Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 01:01 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-j6wf-6qh3-cm45

What to do

AI-suggested

The vulnerability has been resolved in the Linux kernel. Users should apply the official kernel updates that include the fix for process_string() to ensure correct handling of trace event strings referencing arrays. Since this is a kernel-level fix, updating to the patched kernel version is the recommended remediation. No additional mitigations are indicated.

Description

CVE-2024-57930 is a medium severity vulnerability in the Linux kernel tracing subsystem. It addresses a bug in the process_string() function used during event registration to verify safe string references in trace events. The fix allows process_string() to recognize safe references to arrays, preventing false positives that could otherwise flag valid trace event strings as unsafe. This resolves issues where TRACE_EVENT() macros assign string addresses that may be incorrectly considered unsafe, potentially causing incorrect handling of trace data.

Impact

The vulnerability could cause false positives in kernel tracing event validation, potentially leading to incorrect handling or rejection of valid trace events. The CVSS score of 5.5 with an impact primarily on availability (A:H) indicates that exploitation could cause denial of service or instability in kernel tracing but does not affect confidentiality or integrity. There is no indication of active exploitation or impact on data confidentiality or integrity.

Summary

The vulnerability involves the Linux kernel's tracing subsystem, specifically the process_string() function used by test_event_printk() to validate string references in TRACE_EVENT() TP_printk() format strings containing "%s". Previously, process_string() could incorrectly flag safe references to arrays of strings as unsafe, leading to false positives. The patch modifies process_string() to allow references to arrays where the record field is an index, ensuring these references are considered safe. This prevents bugs where trace events might reference freed strings or be incorrectly flagged, improving the reliability of kernel tracing.

References

Community reviews

Loading reviews…