In the Linux kernel, the following vulnerability has been resolved: kcm: use WRITE_ONCE() when changing lower socket callbacks kcm_atta…
CVE-2026-74262 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-74262?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 4.6
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
kcm: use WRITE_ONCE() when changing lower socket callbacks
kcm_attach() replaces a live lower TCP socket's sk_data_ready and
sk_write_space callbacks with KCM handlers, and kcm_unattach() restores
them later. Those callback-pointer updates are still plain stores even
though the same fields can be read and invoked concurrently on other
CPUs.
If another CPU observes an older callback snapshot after the live field
has already been restored, callback execution can run with a mismatched
target and sk_user_data state, leading to stale or misdirected wakeups.
Use WRITE_ONCE() for the callback replacement and restore operations so
these shared callback fields follow the same visibility contract already
established by the earlier 4022 fixes.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/0cb3e2f40679032c1aa2186280a86e5ead0161ee
- git.kernel.org/stable/c/11faefd11ce2448bac7279ab302dd1954a6547fe
- git.kernel.org/stable/c/47186409c092cd7dd70350999186c700233e854d
- git.kernel.org/stable/c/9684fff87124b201e11dea01ded9173025359a0f
- git.kernel.org/stable/c/b4ccd6eef671d7c44a30123cd29f3acf3de8468e
- git.kernel.org/stable/c/b8c90823cdfb5f3d22f261aeb3e9066612853c36
- git.kernel.org/stable/c/f01fb6138f8eb606b56ce9158e2d8b72352c53f4
- git.kernel.org/stable/c/fa26e4606aed0f7fe793c325506adeda1d847a43
Merged from NVD. Last updated 23 Oct 2026. All vulnerabilities · RSS · JSON