🛡️ CVE-2024-35917 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

s390/bpf: Fix bpf_plt pointer arithmetic

In the Linux kernel, the following vulnerability has been resolved:

s390/bpf: Fix bpf_plt pointer arithmetic

Kui-Feng Lee reported a crash on s390x triggered by the

dummy_st_ops/dummy_init_ptr_arg test [1]:

[<0000000000000002>] 0x2

[<00000000009d5cde>] bpf_struct_ops_test_run+0x156/0x250

[<000000000033145a>] __sys_bpf+0xa1a/0xd00

[<00000000003319dc>] __s390x_sys_bpf+0x44/0x50

[<0000000000c4382c>] __do_syscall+0x244/0x300

[<0000000000c59a40>] system_call+0x70/0x98

This is caused by GCC moving memcpy() after assignments in

bpf_jit_plt(), resulting in NULL pointers being written instead of

the return and the target addresses.

Looking at the GCC internals, the reordering is allowed because the

alias analysis thinks that the memcpy() destination and the assignments'

left-hand-sides are based on different objects: new_plt and

bpf_plt_ret/bpf_plt_target respectively, and therefore they cannot

alias.

This is in turn due to a violation of the C standard:

When two pointers are subtracted, both shall point to elements of the

same array object, or one past the last element of the array object

...

From the C's perspective, bpf_plt_ret and bpf_plt are distinct objects

and cannot be subtracted. In the practical terms, doing so confuses the

GCC's alias analysis.

The code was written this way in order to let the C side know a few

offsets defined in the assembly. While nice, this is by no means

necessary. Fix the noncompliance by hardcoding these offsets.

[1] https://lore.kernel.org/bpf/c9923c1d-971d-4022-8dc8-1364e929d34c@gmail.com/

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-35917 is recorded against 2 packages.

  • kernel (from 6.7.0 up to 6.8.5)
  • linux-kernel

Timeline and source

Published on 19 May 2024 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-35917 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-05-19
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.7.0 6.8.5
linux-kernel

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-35917 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024