Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43010bpf: Reject sleepable kprobe_multi programs at attach time

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43010, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0dcac272540613d41c05e89679e4ddb978b612f1 – < c2b5e13dee9cc83e664daf4c13077dcc618a44e9
    • affected 0dcac272540613d41c05e89679e4ddb978b612f1 – < 89327ed787746a7aa4db3c97f91d2e294228932b
    • affected 0dcac272540613d41c05e89679e4ddb978b612f1 – < d97b19fe5265f7901b2c862f88a4eb1b129a0b61
    • affected 0dcac272540613d41c05e89679e4ddb978b612f1 – < dc9a060d76c12b23c5f378ee115d5e5d03d8bbf3
    • affected 0dcac272540613d41c05e89679e4ddb978b612f1 – < f952157e695fd434bdc05af63a703bb082a78717
    • affected 0dcac272540613d41c05e89679e4ddb978b612f1 – < eb7024bfcc5f68ed11ed9dd4891a3073c15f04a8
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43010 badge
[![CVE-2026-43010](https://cveledger.app/badge/CVE-2026-43010.svg)](https://cveledger.app/cve/CVE-2026-43010)

Record last updated .