CVE-2024-56675: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors

Published Dec 27, 2024
·
Updated

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

bpf: Fix UAF via mismatching bpfprog/attachment RCU flavors

Uprobes always use bpfprogrunarrayuprobe() under tasks-trace-RCU protection. But it is possible to attach a non-sleepable BPF program to a uprobe, and non-sleepable BPF programs are freed via normal RCU (see bpfprogputnoref()). This leads to UAF of the bpfprog because a normal RCU grace period does not imply a tasks-trace-RCU grace period.

Fix it by explicitly waiting for a tasks-trace-RCU grace period after removing the attachment of a bpfprog to a perfevent.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

11 affected componentsFixes available
Linux Linux kernel>=6.0<6.1.121
Linux Linux kernel>=6.2<6.6.67
Linux Linux kernel>=6.7<6.12.6
Linux Linux kernel=6.13-rc1
Linux Linux kernel=6.13-rc2
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Compensating control

    After removing the attachment of a bpf_prog to a perf_event (involving uprobe attachment removal), explicitly wait for a tasks-trace-RCU grace period before completing cleanup, since a normal RCU grace period does not imply a tasks-trace-RCU grace period.

Event History

Dec 27, 2024
CVE Published
via MITRE·03:06 PM
Data Sourced
via MITRE·03:06 PM
Description
Data Sourced
via NVD·03:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·04:02 PM
DescriptionSeverityAffected Software
Mar 27, 2025
Data Sourced
via Launchpad·06:47 PM
Description
May 6, 2025
Data Sourced
via Ubuntu·06:56 PM
RemedyDescriptionSeverityAffected Software
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-56675?

CVE-2024-56675 is considered to have a moderate severity impact due to potential use-after-free vulnerabilities in the Linux kernel.

2

How do I fix CVE-2024-56675?

To fix CVE-2024-56675, update the Linux kernel to the latest patched version that resolves the vulnerability.

3

Which versions of the Linux kernel are affected by CVE-2024-56675?

CVE-2024-56675 affects Linux kernel versions from 6.0 up to and including 6.1.121, 6.2 to 6.6.67, and 6.7 up to 6.12.6.

4

What does CVE-2024-56675 impact in the Linux kernel?

CVE-2024-56675 impacts the BPF (Berkeley Packet Filter) system, specifically related to uprobes and improper attachment of BPF programs.

5

Is there a workaround for CVE-2024-56675 if I cannot update the kernel?

There are no widely recommended workarounds for CVE-2024-56675, and updating is the best solution to mitigate the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203