CVE-2024-26591

bpf: Fix re-attachment branch in bpf_tracing_prog_attach

MEDIUM

5.5

CVSS Score

Published: February 22, 2024 at 04:21 PM UTC

Updated: June 17, 2026 at 07:17 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: <TASK> ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 5.15.1485.13 ≤ v < 5.15.1485.13 ≤ v < 6.1.755.13 ≤ v < 6.6.145.13 ≤ v < 6.7.25.13 ≤ v < 6.85.16.0 ≤ v < 6.1.756.2.0 ≤ v < 6.6.146.7.0 ≤ v < 6.7.25.13f3a95075549e0e5c36db922caf86847db7a35403

Vendor states this is fixed in 50ae82f080cf87e84828f066c31723b781d68f5b (fixed)

Vendor states this is fixed in 6cc9c0af0aa06f781fa515a1734b1a4239dfd2c0 (fixed)

Vendor states this is fixed in 715d82ba636cb3629a6e18a33bb9dbe53f9936ee (fixed)

Vendor states this is fixed in 8c8bcd45e9b10eef12321f08d2e5be33d615509c (fixed)

Vendor states this is fixed in a7b98aa10f895e2569403896f2d19b73b6c95653 (fixed)

Vendor states this is fixed in 5.13 (unaffected)

Vendor states this is fixed in 5.15.148 (unaffected)

Vendor states this is fixed in 6.1.75 (unaffected)

Vendor states this is fixed in 6.6.14 (unaffected)

Vendor states this is fixed in 6.7.2 (unaffected)

Vendor states this is fixed in 6.8 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references