CVE-2024-35895: bpf, sockmap: Prevent lock inversion deadlock in map delete elem
First published: Sun May 19 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Prevent lock inversion deadlock in map delete elem syzkaller started using corpuses where a BPF tracing program deletes elements from a sockmap/sockhash map. Because BPF tracing programs can be invoked from any interrupt context, locks taken during a map_delete_elem operation must be hardirq-safe. Otherwise a deadlock due to lock inversion is possible, as reported by lockdep: CPU0 CPU1 ---- ---- lock(&htab->buckets[i].lock); local_irq_disable(); lock(&host->lock); lock(&htab->buckets[i].lock); <Interrupt> lock(&host->lock); Locks in sockmap are hardirq-unsafe by design. We expects elements to be deleted from sockmap/sockhash only in task (normal) context with interrupts enabled, or in softirq context. Detect when map_delete_elem operation is invoked from a context which is _not_ hardirq-unsafe, that is interrupts are disabled, and bail out with an error. Note that map updates are not affected by this issue. BPF verifier does not allow updating sockmap/sockhash from a BPF tracing program today.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/kernel | <5.4.274 | 5.4.274 |
| redhat/kernel | <5.10.215 | 5.10.215 |
| redhat/kernel | <5.15.154 | 5.15.154 |
| redhat/kernel | <6.1.85 | 6.1.85 |
| redhat/kernel | <6.6.26 | 6.6.26 |
| redhat/kernel | <6.8.5 | 6.8.5 |
| redhat/kernel | <6.9 | 6.9 |
| Linux kernel | >=4.20<5.4.274 | |
| Linux kernel | >=5.5<5.10.215 | |
| Linux kernel | >=5.11<5.15.154 | |
| Linux kernel | >=5.16<6.1.85 | |
| Linux kernel | >=6.2<6.6.26 | |
| Linux kernel | >=6.7<6.8.5 | |
| Linux kernel | =6.9-rc1 | |
| Linux kernel | =6.9-rc2 | |
| Debian | =10.0 | |
| debian/linux | 5.10.223-1 5.10.234-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.16-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/668b3074aa14829e2ac2759799537a93b60fef86
- https://git.kernel.org/stable/c/6af057ccdd8e7619960aca1f0428339f213b31cd
- https://git.kernel.org/stable/c/a44770fed86515eedb5a7c00b787f847ebb134a5
- https://git.kernel.org/stable/c/d1e73fb19a4c872d7a399ad3c66e8ca30e0875ec
- https://git.kernel.org/stable/c/dd54b48db0c822ae7b520bc80751f0a0a173ef75
- https://git.kernel.org/stable/c/f7990498b05ac41f7d6a190dc0418ef1d21bf058
- https://git.kernel.org/stable/c/ff91059932401894e6c86341915615c5eb0eca48
- https://launchpad.net/bugs/cve/CVE-2024-35895
- https://access.redhat.com/security/cve/CVE-2024-35895
- https://lore.kernel.org/linux-cve-announce/2024051950-CVE-2024-35895-cb33@gregkh/T
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2281678
- https://access.redhat.com/errata/RHSA-2024:6268
- https://access.redhat.com/errata/RHSA-2024:6267
- https://access.redhat.com/errata/RHSA-2024:6997
- https://bugzilla.redhat.com/show_bug.cgi?id=2281677
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35895
- https://nvd.nist.gov/vuln/detail/CVE-2024-35895
- https://security-tracker.debian.org/tracker/CVE-2024-35895
- https://ubuntu.com/security/CVE-2024-35895
- https://git.kernel.org/linus/ff91059932401894e6c86341915615c5eb0eca48
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
Frequently Asked Questions
What is the severity of CVE-2024-35895?
CVE-2024-35895 has been classified as a medium severity vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-35895?
CVE-2024-35895 affects multiple versions of the Linux kernel prior to 5.4.274, 5.10.215, 5.15.154, 6.1.85, 6.6.26, and some Debian versions.
How do I fix CVE-2024-35895?
To fix CVE-2024-35895, upgrade the Linux kernel to the latest patched version specified for your distribution.
What components are involved in CVE-2024-35895?
CVE-2024-35895 involves issues in the BPF (Berkeley Packet Filter) and sockmap/sockhash mechanisms within the Linux kernel.
Is CVE-2024-35895 exploitable remotely?
Yes, CVE-2024-35895 could potentially be exploited in environments where BPF programs are used to manage sockmaps.
- agent/title
- agent/type
- collector/epss-latest
- source/FIRST
- agent/epss
- collector/launchpad-cve
- source/Launchpad
- agent/author
- agent/first-publish-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-35895
- agent/software-canonical-lookup
- agent/trending
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/remedy
- agent/last-modified-date
- agent/severity
- agent/references
- agent/source
- agent/tags
- collector/usn-cve
- source/Ubuntu
- collector/security-tracker-debian
- source/Debian
- agent/softwarecombine
- agent/description
- agent/event
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-cve
- package-manager/redhat
- package-manager/debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/4.20
- version/linux kernel/5.5
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.9-rc1
- version/linux kernel/6.9-rc2
- vendor/debian
- canonical/debian
- version/debian/10.0