CVE-2026-74262

kcm: use WRITE_ONCE() when changing lower socket callbacks

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:57 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.6ab7ac4eb9832e32a09f4e8042705484d2fb0aad3
Vendor states this is fixed in 0cb3e2f40679032c1aa2186280a86e5ead0161ee (fixed)
Vendor states this is fixed in 11faefd11ce2448bac7279ab302dd1954a6547fe (fixed)
Vendor states this is fixed in 47186409c092cd7dd70350999186c700233e854d (fixed)
Vendor states this is fixed in 9684fff87124b201e11dea01ded9173025359a0f (fixed)
Vendor states this is fixed in b4ccd6eef671d7c44a30123cd29f3acf3de8468e (fixed)
Vendor states this is fixed in b8c90823cdfb5f3d22f261aeb3e9066612853c36 (fixed)
Vendor states this is fixed in f01fb6138f8eb606b56ce9158e2d8b72352c53f4 (fixed)
Vendor states this is fixed in fa26e4606aed0f7fe793c325506adeda1d847a43 (fixed)
Vendor states this is fixed in 4.6 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card