CVE-2026-99774
What it is
In the Linux kernel, the following vulnerability has been resolved: xfrm: espintcp: reorder operations within espintcp_init_sk When enabled on a socket, espintcp sets the socket callbacks to its own before it has finished setting up its context and published it as icsk_ulp_data. Any one of those callbacks that gets called before will dereference a NULL icsk_ulp_data. Fix this by reording the operations, and add memory barriers to ensure callers will have a struct espintcp_ctx available. Add a few WRITE_ONCE/READ_ONCE too while we're there.
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
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: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 6653f281a84dfc050042b837fbf0a1ab87f8f645
- Linux < d50065a04b8b2edd9215a1960a48c4a4667a5b8c
- Linux < 3eac7cf352cedd05215bdc7e9786c3ee4b4b43b2
- Linux < f9a11716c8445b496e9fafeec7e8412d384d02e2
- Linux 5.6
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-99774.md and follow it. Check whether this project is affected by CVE-2026-99774. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.