CVE-2026-43091
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- Linux Kernel < 6.6.136
- Linux Kernel < 6.12.83
- Linux Kernel < 6.18.24
- Linux Kernel < 6.19.14
- Linux Kernel 7.0
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43091.md and follow it. Check whether this project is affected by CVE-2026-43091. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/069daad4f2ae9c5c108131995529d5f02392c446
- https://git.kernel.org/stable/c/33a3149dd81a1e2f52b80ee1e0fc380b39f3d028
- https://git.kernel.org/stable/c/3733fce2871c9bca9dd18a1a23b1432ea215a094
- https://git.kernel.org/stable/c/438b1f668ad58f46ce699bb48e4698a7839e3f9e
- https://git.kernel.org/stable/c/b66920a3348c0f63ba18365248fa21fbf0b3a937
References
- https://git.kernel.org/stable/c/069daad4f2ae9c5c108131995529d5f02392c446
- https://git.kernel.org/stable/c/33a3149dd81a1e2f52b80ee1e0fc380b39f3d028
- https://git.kernel.org/stable/c/3733fce2871c9bca9dd18a1a23b1432ea215a094
- https://git.kernel.org/stable/c/438b1f668ad58f46ce699bb48e4698a7839e3f9e
- https://git.kernel.org/stable/c/b2faee12538b5b008eaef65a4201eb29cb5cefb3
- https://git.kernel.org/stable/c/b66920a3348c0f63ba18365248fa21fbf0b3a937