{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93246 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93246 is a memory corruption vulnerability in Linux, published on 24 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-93246 and fix it if it is affected.\n\nWhat it is: CVE-2026-93246 is a memory corruption vulnerability in Linux, published on 24 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-93246 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-93246/ (Markdown: https://insights.sbomify.com/CVE-2026-93246/index.md)","id":"CVE-2026-93246","markdown":"https://insights.sbomify.com/CVE-2026-93246/index.md","name":"CVE-2026-93246","record":{"aliases":["DEBIAN-CVE-2026-93246","GHSA-52xx-jr85-g6wq","UBUNTU-CVE-2026-93246"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"An out-of-bounds read in the octeontx2-af kernel driver can cause a crash or leak memory when debug options are enabled during boot.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nocteontx2-af: fix out-of-bounds read setting MSI-X irq affinity\n\nrvu_register_interrupts() walks every MSI-X vector and uses strstr()\nto match \"Mbox\" or \"FLR\" in irq_name before pinning those interrupts\nto CPU 0. irq_name is a per-vector NAME_SIZE buffer, but not every\nslot is populated before this loop runs. strstr() keeps scanning until\nit finds a NUL terminator, so an uninitialized slot can trigger a KASAN\nslab-out-of-bounds read at boot when debug options are enabled.\n\nUse strnstr() with NAME_SIZE to bound the search within each vector's\nname buffer.","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":"octeontx2-af: fix out-of-bounds read setting MSI-X irq affinity","id":"CVE-2026-93246","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Bluetooth: mgmt: fix 'hdev-\u003ediscovery.uuids' NULL dereference","id":"CVE-2026-93247"},"packages":[],"prev":{"headline":"apparmor: policy_int make sure list heads are initialized before fail path","id":"CVE-2026-93245"},"products":["Linux"],"published":"2026-09-24","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-19","vendors":["Linux"]},"summary":"An out-of-bounds read in the octeontx2-af kernel driver can cause a crash or leak memory when debug options are enabled during boot.","url":"https://insights.sbomify.com/CVE-2026-93246/"}