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-43376

ksmbd: fix use-after-free by using call_rcu() for oplock_info

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free by using call_rcu() for oplock_info ksmbd currently frees oplock_info immediately using kfree(), even though it is accessed under RCU read-side critical sections in places like opinfo_get() and proc_show_files(). Since there is no RCU grace period delay between nullifying the pointer and freeing the memory, a reader can still access oplock_info structure after it has been freed. This can leads to a use-after-free especially in opinfo_get() where atomic_inc_not_zero() is called on already freed memory. Fix this by switching to deferred freeing using call_rcu().

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 3 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-43376, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.44% · top 61% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 296cb5457cc6f4a754c4ae29855f8a253d52bcc6 – < 302fef75512b2c8329a3f5efab1ae7ba2562387a
    • affected d54ab1520d43e95f9b2e22d7a05fc9614192e5a5 – < 08aa9f3c8cf4d0bee44df540dfe34e8d64069f2c
    • affected 18b4fac5ef17f77fed9417d22210ceafd6525fc7 – < 1d6abf145615dbfe267ce3b0a271f95e3780e18e
    • affected 18b4fac5ef17f77fed9417d22210ceafd6525fc7 – < ce8507ee82c888126d8e7565e27c016308d24cde
    • affected 18b4fac5ef17f77fed9417d22210ceafd6525fc7 – < 1dfd062caa165ec9d7ee0823087930f3ab8a6294
    • affected d73686367ad68534257cd88a36ca3c52cb8b81d8
    • affected 6.6.88 – < 6.6.130
    • affected 6.12.25 – < 6.12.78
    • affected 6.14.4 – < 6.15
  • Linux · Linux

    • affected 6.15
    • unaffected < 6.15
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.19 – ≤ 6.18.*
    • unaffected 6.19.9 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .