{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72390 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72390 is a high-severity use after free 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-72390 and fix it if it is affected.\n\nWhat it is: CVE-2026-72390 is a high-severity use after free 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-72390 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-72390/ (Markdown: https://insights.sbomify.com/CVE-2026-72390/index.md)","id":"CVE-2026-72390","markdown":"https://insights.sbomify.com/CVE-2026-72390/index.md","name":"CVE-2026-72390","record":{"aliases":["BELL-CVE-2026-72390","DEBIAN-CVE-2026-72390","GHSA-6rv6-hxhf-8gw6","UBUNTU-CVE-2026-72390"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"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 teql scheduler allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nnet/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF\n\nThe teql master-\u003eslaves singly linked list is not protected against\nmultiple writes. It can be mod'ed concurently from teql_master_xmit(),\nteql_dequeue(), teql_init() and teql_destroy() without holding any list\nlock or RCU protection.\n\nzdi-disclosures@trendmicro.com has demonstrated that the qdisc is freed\nafter an RCU grace period, but teql_master_xmit() running on another\nCPU can still hold a stale pointer into the list, resulting in a\nslab-use-after-free:\n\nBUG: KASAN: slab-use-after-free in teql_master_xmit+0xf0f/0x16b0\nRead of size 8 at addr ffff888013fb0440 by task poc/332\nFreed 512-byte region [ffff888013fb0400, ffff888013fb0600) (kmalloc-512)\n\nThe fix?\nAdd a per-master slaves_lock spinlock that serializes all mutations of\nmaster-\u003eslaves and the NEXT_SLAVE() links in teql_destroy() and\nteql_qdisc_init(). teql_master_xmit() also takes the same slaves_lock\naround those updates.\nAnnotate master-\u003eslaves and the per-slave -\u003enext pointer with __rcu and\nuse the appropriate RCU accessors everywhere they are touched:\nrcu_assign_pointer() on the writer side (under slaves_lock),\nrcu_dereference_protected() for the writer-side loads (also under\nslaves_lock), rcu_dereference_bh() for the loads in teql_master_xmit() and\nrtnl_dereference() for the loads in teql_master_open()/teql_master_mtu(),\nwhich run under RTNL.\nPair this with rcu_read_lock_bh()/rcu_read_unlock_bh() around the list\ntraversal in teql_master_xmit(), so that readers either observe a fully\nlinked list or are deferred until the in-flight mutation completes. The two\nearly-return paths in teql_master_xmit() are updated to release the RCU-bh\nread-side critical section before returning, since leaving it held would\ndisable BH on that CPU for good.","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":"net/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF","id":"CVE-2026-72390","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy","id":"CVE-2026-72391"},"packages":[],"prev":{"headline":"bridge: stp: Fix a potential use-after-free when deleting a bridge","id":"CVE-2026-72389"},"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 teql scheduler allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-72390/"}