Answer in brief
CVE-2026-74262 records a Unknown severity vulnerability in kcm: use WRITE_ONCE() when changing lower socket callbacks. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-74262 records a Unknown severity vulnerability in kcm: use WRITE_ONCE() when changing lower socket callbacks. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <0cb3e2f40679032c1aa2186280a86e5ead0161ee || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <fa26e4606aed0f7fe793c325506adeda1d847a43 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <b4ccd6eef671d7c44a30123cd29f3acf3de8468e || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <b8c90823cdfb5f3d22f261aeb3e9066612853c36 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <11faefd11ce2448bac7279ab302dd1954a6547fe || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <f01fb6138f8eb606b56ce9158e2d8b72352c53f4 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <9684fff87124b201e11dea01ded9173025359a0f || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <47186409c092cd7dd70350999186c700233e854d | 0cb3e2f40679032c1aa2186280a86e5ead0161ee, fa26e4606aed0f7fe793c325506adeda1d847a43, b4ccd6eef671d7c44a30123cd29f3acf3de8468e, b8c90823cdfb5f3d22f261aeb3e9066612853c36, 11faefd11ce2448bac7279ab302dd1954a6547fe, f01fb6138f8eb606b56ce9158e2d8b72352c53f4, 9684fff87124b201e11dea01ded9173025359a0f, 47186409c092cd7dd70350999186c700233e854d |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <0cb3e2f40679032c1aa2186280a86e5ead0161ee || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <fa26e4606aed0f7fe793c325506adeda1d847a43 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <b4ccd6eef671d7c44a30123cd29f3acf3de8468e || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <b8c90823cdfb5f3d22f261aeb3e9066612853c36 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <11faefd11ce2448bac7279ab302dd1954a6547fe || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <f01fb6138f8eb606b56ce9158e2d8b72352c53f4 || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <9684fff87124b201e11dea01ded9173025359a0f || >=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <47186409c092cd7dd70350999186c700233e854d | 0cb3e2f40679032c1aa2186280a86e5ead0161ee, fa26e4606aed0f7fe793c325506adeda1d847a43, b4ccd6eef671d7c44a30123cd29f3acf3de8468e, b8c90823cdfb5f3d22f261aeb3e9066612853c36, 11faefd11ce2448bac7279ab302dd1954a6547fe, f01fb6138f8eb606b56ce9158e2d8b72352c53f4, 9684fff87124b201e11dea01ded9173025359a0f, 47186409c092cd7dd70350999186c700233e854d |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.