CVE-2024-57934 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: fgraph: Add READ_ONCE() when accessing fgraph_array[] In __ftrace_return_to_handler(), a loop iterates over the fgraph_array[] elements, which are fgraph_ops. The loop checks if an element is a fgraph_stub to prevent using a fgraph_stub afterward. However, if the compiler reloads fgraph_array[] after this check, it might race with an update to fgraph_array[] that introduces a fgraph_stub. This could result in the stub being processed, but the stub contains a null "func_hash" field, leading to a NULL pointer dereference. To ensure that the gops compared against the fgraph_stub matches the gops processed later, add a READ_ONCE(). A similar patch appears in commit 63a8dfb ("function_graph: Add READ_ONCE() when accessing fgraph_array[]").

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-01-22	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-01-22

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
4.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.0	3.6	[email protected]
4.7	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:H) Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.0	3.6	134c704f-9b21-4f2e-91b3-4a467353bcc0

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

4.7

3.1

MEDIUM

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.0

3.6

[email protected]

4.7

3.1

MEDIUM

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

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H): Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.0

3.6

134c704f-9b21-4f2e-91b3-4a467353bcc0

OS Trackers for CVE-2024-57934

vendor	priority	summary	link
`debian`	unimportant	CVE-2024-57934 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2024-57934
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2024-57934
`suse`	medium	CVE-2024-57934 severity moderate: SUSE including 52 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 268 product×package rows across 46 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 12 SP5, … (46 product lines)): Known Not Affected 242, Fixed 26.	https://www.suse.com/security/cve/CVE-2024-57934/
`ubuntu`	medium	CVE-2024-57934 medium priority: Ubuntu including 130 source packages (linux, linux-allwinner-5.19, …), 1040 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): DNE 713, ignored 146, not-affected 106, released 75.	https://ubuntu.com/security/CVE-2024-57934

Affected software / configurations for CVE-2024-57934

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 6.11, < 6.12.9	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.13	cpe:2.3:o:linux:linux_kernel:6.13:rc1::::::
linux	linux_kernel	6.13	cpe:2.3:o:linux:linux_kernel:6.13:rc2::::::
linux	linux_kernel	6.13	cpe:2.3:o:linux:linux_kernel:6.13:rc3::::::
linux	linux_kernel	6.13	cpe:2.3:o:linux:linux_kernel:6.13:rc4::::::
linux	linux_kernel	6.13	cpe:2.3:o:linux:linux_kernel:6.13:rc5::::::

References for CVE-2024-57934

URL	Tags
https://git.kernel.org/stable/c/b68b2a3fbacc7be720ef589d489bcacdd05c6d38	Patch
https://git.kernel.org/stable/c/d65474033740ded0a4fe9a097fce72328655b41d	Patch

URL

CVE-2024-57934 | fgraph: Add READ_ONCE() when accessing fgraph_array[]

Exploit prediction scoring system (EPSS) score for CVE-2024-57934

Common vulnerability scoring system (CVSS) metrics for CVE-2024-57934

Weakness enumeration for CVE-2024-57934

OS Trackers for CVE-2024-57934

Affected software / configurations for CVE-2024-57934

References for CVE-2024-57934