CVE-2026-63919
What it is
In the Linux kernel, the following vulnerability has been resolved: xfrm: input: hold netns during deferred transport reinjection Transport-mode reinjection stores a struct net pointer in skb->cb and uses it later from xfrm_trans_reinject(). That pointer must stay valid until the deferred callback runs. Take a netns reference when queueing deferred reinjection work and drop it after the callback completes. Use maybe_get_net() so the queueing path does not revive a namespace that is already being torn down. This keeps the existing workqueue design and fixes the netns lifetime handling in one place for all users of xfrm_trans_queue_net().
At a glance
- Exploitability
- Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.7% 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.7% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.7% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.259
- Linux Kernel < 5.15.210
- Linux Kernel < 6.1.176
- Linux Kernel < 6.6.143
- Linux Kernel < 6.12.93
- Linux Kernel < 6.18.35
- Linux Kernel < 7.0.12
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/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-63919.md and follow it. Check whether this project is affected by CVE-2026-63919. 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/2df7059a18afb7d3aee6c36cad5d371c198111d4
- https://git.kernel.org/stable/c/48ce101cd630d6745b6923b5bad8358bc4c119da
- https://git.kernel.org/stable/c/55ddfc41451f01c588089cd74957a05311b6f202
- https://git.kernel.org/stable/c/7ee59eda8820b758ed29e1cd3222359c7b97302c
- https://git.kernel.org/stable/c/8dfabcba6a943a7a02ebe1e1637c361ba96acbaa
- https://git.kernel.org/stable/c/9f67a36e91bb50d358760f381f233913fe5c09f8
- https://git.kernel.org/stable/c/9f7ebb45a83afc3216e855e57d51bb4bc9b5232e
- https://git.kernel.org/stable/c/c16f74dc1d75d0e2e7670076d5375deda110ebeb
References
- https://git.kernel.org/stable/c/2df7059a18afb7d3aee6c36cad5d371c198111d4
- https://git.kernel.org/stable/c/48ce101cd630d6745b6923b5bad8358bc4c119da
- https://git.kernel.org/stable/c/55ddfc41451f01c588089cd74957a05311b6f202
- https://git.kernel.org/stable/c/7ee59eda8820b758ed29e1cd3222359c7b97302c
- https://git.kernel.org/stable/c/8dfabcba6a943a7a02ebe1e1637c361ba96acbaa
- https://git.kernel.org/stable/c/9f67a36e91bb50d358760f381f233913fe5c09f8
- https://git.kernel.org/stable/c/9f7ebb45a83afc3216e855e57d51bb4bc9b5232e
- https://git.kernel.org/stable/c/c16f74dc1d75d0e2e7670076d5375deda110ebeb