{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72076 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72076 is a 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-72076 and fix it if it is affected.\n\nWhat it is: CVE-2026-72076 is a 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-72076 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-72076/ (Markdown: https://insights.sbomify.com/CVE-2026-72076/index.md)","id":"CVE-2026-72076","markdown":"https://insights.sbomify.com/CVE-2026-72076/index.md","name":"CVE-2026-72076","record":{"aliases":["BELL-CVE-2026-72076","DEBIAN-CVE-2026-72076","GHSA-cxr9-fhw6-hh88","UBUNTU-CVE-2026-72076"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A local attacker can trigger an out-of-bounds read in the IMS PCU driver's debug logging, potentially leaking kernel memory contents.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nInput: ims-pcu - fix out-of-bounds read in ims_pcu_irq() debug logging\n\nThe debug logging in ims_pcu_irq() unconditionally prints data from\npcu-\u003eurb_in_buf. However, if the interrupt fired for pcu-\u003eurb_ctrl, the\nactual data resides in pcu-\u003eurb_ctrl_buf. If urb-\u003eactual_length for the\ncontrol URB exceeds pcu-\u003emax_in_size, this leads to an out-of-bounds\nread.\n\nFix this by printing from the correct buffer associated with the URB.","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":"Input: ims-pcu - fix out-of-bounds read in ims_pcu_irq() debug logging","id":"CVE-2026-72076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Input: ims-pcu - fix firmware leak in async update","id":"CVE-2026-72077"},"packages":[],"prev":{"headline":"Input: ims-pcu - fix race condition in reset_device sysfs callback","id":"CVE-2026-72075"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A local attacker can trigger an out-of-bounds read in the IMS PCU driver's debug logging, potentially leaking kernel memory contents.","url":"https://insights.sbomify.com/CVE-2026-72076/"}