Use of a Non-reentrant Function in a Concurrent Context The advisory has been revoked - it doesn't affect any version of package kernel-tools (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL10-KERNELTOOLS-16359556
- published4 May 2026
- disclosed1 May 2026
Introduced: 1 May 2026
CVE-2026-43010 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:10.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-tools package and not the kernel-tools package as distributed by RHEL.
In the Linux kernel, the following vulnerability has been resolved:
bpf: Reject sleepable kprobe_multi programs at attach time
kprobe.multi programs run in atomic/RCU context and cannot sleep. However, bpf_kprobe_multi_link_attach() did not validate whether the program being attached had the sleepable flag set, allowing sleepable helpers such as bpf_copy_from_user() to be invoked from a non-sleepable context.
This causes a "sleeping function called from invalid context" splat:
BUG: sleeping function called from invalid context at ./include/linux/uaccess.h:169 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1787, name: sudo preempt_count: 1, expected: 0 RCU nest depth: 2, expected: 0
Fix this by rejecting sleepable programs early in bpf_kprobe_multi_link_attach(), before any further processing.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2464451
- https://access.redhat.com/security/cve/CVE-2026-43010
- https://git.kernel.org/stable/c/dc9a060d76c12b23c5f378ee115d5e5d03d8bbf3
- https://git.kernel.org/stable/c/eb7024bfcc5f68ed11ed9dd4891a3073c15f04a8
- https://git.kernel.org/stable/c/f952157e695fd434bdc05af63a703bb082a78717
- https://git.kernel.org/stable/c/89327ed787746a7aa4db3c97f91d2e294228932b
- https://git.kernel.org/stable/c/d97b19fe5265f7901b2c862f88a4eb1b129a0b61
- https://git.kernel.org/stable/c/c2b5e13dee9cc83e664daf4c13077dcc618a44e9