{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97915 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97915 is a vulnerability in Linux, published on 25 Sep 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-97915 and fix it if it is affected.\n\nWhat it is: CVE-2026-97915 is a vulnerability in Linux, published on 25 Sep 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-97915 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-97915/ (Markdown: https://insights.sbomify.com/CVE-2026-97915/index.md)","id":"CVE-2026-97915","markdown":"https://insights.sbomify.com/CVE-2026-97915/index.md","name":"CVE-2026-97915","record":{"aliases":["AZL-104256","BELL-CVE-2026-97915","DEBIAN-CVE-2026-97915","GHSA-qr56-qc89-442x","UBUNTU-CVE-2026-97915"],"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 missing NUL-termination check in the Linux kernel's Intel VPU driver allows local attackers to read adjacent memory via debug logs.","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\naccel/ivpu: Limit firmware log name prints to field size\n\nThe name in struct vpu_tracing_buffer_header is a fixed-size array\npopulated by the NPU firmware. It is expected to be NUL-terminated,\nbut nothing on the host side enforces this, so printing it with an\nunbounded string conversion would read past the field if the\nterminator is ever missing and expose adjacent bytes of the shared\ntracing BO through dmesg and the debugfs FW log output.\n\nPrint at most as many characters as the name field holds, so the output\nnever runs past it even if the string is not NUL-terminated.","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":"accel/ivpu: Limit firmware log name prints to field size","id":"CVE-2026-97915","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"accel/ivpu: Validate firmware log buffer metadata","id":"CVE-2026-97916"},"packages":[],"prev":{"headline":"accel: ethosu: Fix ethosu_job_open() return value","id":"CVE-2026-97914"},"products":["Linux"],"published":"2026-09-25","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-10-21","vendors":["Linux"]},"summary":"A missing NUL-termination check in the Linux kernel's Intel VPU driver allows local attackers to read adjacent memory via debug logs.","url":"https://insights.sbomify.com/CVE-2026-97915/"}