{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72124 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72124 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-72124 and fix it if it is affected.\n\nWhat it is: CVE-2026-72124 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-72124 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-72124/ (Markdown: https://insights.sbomify.com/CVE-2026-72124/index.md)","id":"CVE-2026-72124","markdown":"https://insights.sbomify.com/CVE-2026-72124/index.md","name":"CVE-2026-72124","record":{"aliases":["BELL-CVE-2026-72124","DEBIAN-CVE-2026-72124","GHSA-h95p-28wv-6wpp","UBUNTU-CVE-2026-72124"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel CAN","requires_auth":"none","summary":"A race condition in the Linux kernel CAN ISO-TP driver allows concurrent access to TX state, potentially corrupting transfers and causing denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/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\ncan: isotp: serialize TX state transitions under so-\u003erx_lock\n\nThe TX state machine (so-\u003etx.state) is driven from three contexts:\nsendmsg() claiming and progressing a transfer, the RX path consuming\nFlow Control/echo frames, and two hrtimers timing out a stalled\ntransfer. Mixing a lock-free cmpxchg() claim in sendmsg() with\nhrtimer_cancel() calls made under so-\u003erx_lock elsewhere left windows\nwhere a frame or timer callback could act on a state that had already\nmoved on, corrupting an unrelated transfer.\n\nso-\u003erx_lock now covers the full lifecycle of a TX claim: sendmsg()\ntakes it to check so-\u003etx.state is ISOTP_IDLE, switch it to\nISOTP_SENDING, bump so-\u003etx_gen and drain the previous transfer's\ntimers - all as one critical section. isotp_rcv_fc()/isotp_rcv_cf()\nalready run under this lock via isotp_rcv(), and isotp_rcv_echo() now\ntakes it itself, so none of them can ever observe a transfer mid-claim.\nThis also means a transfer can no longer be handed to sendmsg()'s\ncleanup paths (signal or send error) while another thread is\nconcurrently claiming or finishing it, so those paths can cancel\ntimers and reset the state unconditionally.\n\nisotp_release() claims the socket the same way, so a racing sendmsg()\nsees a consistent ISOTP_SHUTDOWN and skips arming its timer or sending.\n\nOnly the hrtimer callbacks stay outside so-\u003erx_lock, since they run\nunder so-\u003erx_lock's cancellation elsewhere and taking it themselves\nwould deadlock. so-\u003etx_gen lets them recognize whether the transfer\nthey timed out is still the one currently active, so they don't\nreport an error against a transfer that has since completed or been\nsuperseded.","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":"can: isotp: serialize TX state transitions under so-\u003erx_lock","id":"CVE-2026-72124","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":"can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER","id":"CVE-2026-72125"},"packages":[],"prev":{"headline":"can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF","id":"CVE-2026-72123"},"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 CAN ISO-TP driver allows concurrent access to TX state, potentially corrupting transfers and causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-72124/"}