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-43091xfrm: Wait for RCU readers during policy netns exit

Description

In the Linux kernel, the following vulnerability has been resolved: xfrm: Wait for RCU readers during policy netns exit xfrm_policy_fini() frees the policy_bydst hash tables after flushing the policy work items and deleting all policies, but it does not wait for concurrent RCU readers to leave their read-side critical sections first. The policy_bydst tables are published via rcu_assign_pointer() and are looked up through rcu_dereference_check(), so netns teardown must also wait for an RCU grace period before freeing the table memory. Fix this by adding synchronize_rcu() before freeing the policy hash tables.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    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-43091, 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 97% of all CVEs (15 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 e1e551bc56302b80ff930c966f9985095fb1b70d – < b2faee12538b5b008eaef65a4201eb29cb5cefb3
    • affected e1e551bc56302b80ff930c966f9985095fb1b70d – < b66920a3348c0f63ba18365248fa21fbf0b3a937
    • affected e1e551bc56302b80ff930c966f9985095fb1b70d – < 438b1f668ad58f46ce699bb48e4698a7839e3f9e
    • affected e1e551bc56302b80ff930c966f9985095fb1b70d – < 3733fce2871c9bca9dd18a1a23b1432ea215a094
    • affected e1e551bc56302b80ff930c966f9985095fb1b70d – < 33a3149dd81a1e2f52b80ee1e0fc380b39f3d028
    • affected e1e551bc56302b80ff930c966f9985095fb1b70d – < 069daad4f2ae9c5c108131995529d5f02392c446
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 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-43091 badge
[![CVE-2026-43091](https://cveledger.app/badge/CVE-2026-43091.svg)](https://cveledger.app/cve/CVE-2026-43091)

Record last updated .