{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72482 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72482 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-72482 and fix it if it is affected.\n\nWhat it is: CVE-2026-72482 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-72482 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-72482/ (Markdown: https://insights.sbomify.com/CVE-2026-72482/index.md)","id":"CVE-2026-72482","markdown":"https://insights.sbomify.com/CVE-2026-72482/index.md","name":"CVE-2026-72482","record":{"aliases":["BELL-CVE-2026-72482","DEBIAN-CVE-2026-72482","GHSA-g7v6-7vr9-25jq","UBUNTU-CVE-2026-72482"],"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 double decrement of a reference counter in the Linux kernel gpib driver allows a use-after-free, potentially enabling code execution or privilege escalation.","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\ngpib: fix double decrement of descriptor_busy in command_ioctl()\n\ncommit d1857f8296dc (\"gpib: fix use-after-free in IO ioctl handlers\")\nintroduced a descriptor_busy reference counter to pin struct\ngpib_descriptor across IO ioctl operations.  In command_ioctl(), the\nerror path inside the loop decrements descriptor_busy and breaks, but\nexecution then falls through to the unconditional decrement after the\nloop, underflowing the counter to -1.\n\nThis re-enables the use-after-free that the original fix was meant to\nprevent: a concurrent close_dev_ioctl() sees descriptor_busy == 0 on\nan actively-used descriptor and frees it.\n\nRemove the early decrement from the error path.  The post-loop\ndecrement already handles all exit paths, matching the correct pattern\nused in read_ioctl() and write_ioctl().","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":"gpib: fix double decrement of descriptor_busy in command_ioctl()","id":"CVE-2026-72482","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"usb: host: max3421: Fix shift-out-of-bounds in max3421_hub_control()","id":"CVE-2026-72483"},"packages":[],"prev":{"headline":"iio: magnetometer: ak8975: fix potential kernel stack memory leak","id":"CVE-2026-72481"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A double decrement of a reference counter in the Linux kernel gpib driver allows a use-after-free, potentially enabling code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-72482/"}