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-43366io_uring/kbuf: check if target buffer list is still legacy on recycle

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 5 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-43366, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected c7fb19428d67dd0a2a78a4f237af01d39c78dc5a – < a7b33671e418fca507feebd1d56e7f4952a4b25c
    • affected c7fb19428d67dd0a2a78a4f237af01d39c78dc5a – < 439a6728ec4641ffad1ca796622c19bc525e570f
    • affected c7fb19428d67dd0a2a78a4f237af01d39c78dc5a – < f3fb54e7a8b4aadcc2836ee463eec8c88709b8aa
    • affected c7fb19428d67dd0a2a78a4f237af01d39c78dc5a – < 50ad880db3013c6fee0ef13781762a39e2e7ef83
    • affected c7fb19428d67dd0a2a78a4f237af01d39c78dc5a – < 97b57f69fee1b61b41acbf37e7720cac9d389fa4
    • affected c7fb19428d67dd0a2a78a4f237af01d39c78dc5a – < c2c185be5c85d37215397c8e8781abf0a69bec1f
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.167 – ≤ 6.1.*
    • 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

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .