{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74262 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74262 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74262 and fix it if it is affected.\n\nWhat it is: CVE-2026-74262 is a high-severity vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74262 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74262/ (Markdown: https://insights.sbomify.com/CVE-2026-74262/index.md)","id":"CVE-2026-74262","markdown":"https://insights.sbomify.com/CVE-2026-74262/index.md","name":"CVE-2026-74262","record":{"aliases":["BELL-CVE-2026-74262","DEBIAN-CVE-2026-74262","GHSA-rv7w-h679-g92g","UBUNTU-CVE-2026-74262"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel's KCM module can cause stale or misdirected wakeups due to unsynchronized socket callback updates.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"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's 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"kcm: use WRITE_ONCE() when changing lower socket callbacks","id":"CVE-2026-74262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"net: wwan: t7xx: check skb_clone in control TX","id":"CVE-2026-74263"},"packages":[],"prev":{"headline":"ALSA: seq: avoid stale FIFO cells during resize","id":"CVE-2026-74261"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's KCM module can cause stale or misdirected wakeups due to unsynchronized socket callback updates.","url":"https://insights.sbomify.com/CVE-2026-74262/"}