GHSA-RV7W-H679-G92G
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-17 06:33In 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": [],
"aliases": [
"CVE-2026-74262"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:25Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nkcm: use WRITE_ONCE() when changing lower socket callbacks\n\nkcm_attach() replaces a live lower TCP socket\u0027s sk_data_ready and\nsk_write_space callbacks with KCM handlers, and kcm_unattach() restores\nthem later. Those callback-pointer updates are still plain stores even\nthough the same fields can be read and invoked concurrently on other\nCPUs.\n\nIf another CPU observes an older callback snapshot after the live field\nhas already been restored, callback execution can run with a mismatched\ntarget and sk_user_data state, leading to stale or misdirected wakeups.\n\nUse WRITE_ONCE() for the callback replacement and restore operations so\nthese shared callback fields follow the same visibility contract already\nestablished by the earlier 4022 fixes.",
"id": "GHSA-rv7w-h679-g92g",
"modified": "2026-08-17T06:33:34Z",
"published": "2026-08-15T06:32:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74262"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/0cb3e2f40679032c1aa2186280a86e5ead0161ee"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/11faefd11ce2448bac7279ab302dd1954a6547fe"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/47186409c092cd7dd70350999186c700233e854d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9684fff87124b201e11dea01ded9173025359a0f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b4ccd6eef671d7c44a30123cd29f3acf3de8468e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b8c90823cdfb5f3d22f261aeb3e9066612853c36"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f01fb6138f8eb606b56ce9158e2d8b72352c53f4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fa26e4606aed0f7fe793c325506adeda1d847a43"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.