{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90112 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90112 is a vulnerability in Linux, published on 17 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-90112 and fix it if it is affected.\n\nWhat it is: CVE-2026-90112 is a vulnerability in Linux, published on 17 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-90112 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-90112/ (Markdown: https://insights.sbomify.com/CVE-2026-90112/index.md)","id":"CVE-2026-90112","markdown":"https://insights.sbomify.com/CVE-2026-90112/index.md","name":"CVE-2026-90112","record":{"aliases":["AZL-102842","BELL-CVE-2026-90112","DEBIAN-CVE-2026-90112","GHSA-8m8v-32h4-xj63","UBUNTU-CVE-2026-90112"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","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 integer overflows in the qlcnic driver ROM parser, causing out-of-bounds reads and potential system crashes or information leaks.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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\nnet: qlcnic: validate unified ROM sections before loading\n\nThe unified ROM parser reads directory, product, and data-descriptor fields\nfrom the firmware file.  Existing validation forms table and data ends with\nunchecked additions and multiplications.  Malformed values can wrap before\nthey are compared with the firmware size.  The parser also dereferences\ntyped pointers at firmware-controlled offsets.\n\nValid descriptor extents alone are insufficient for the consumers.  The\nloader reads a fixed-size bootloader regardless of its declared size, the\nversion parser assumes a 17-byte tail, and a partial final firmware word is\nread as a full u64.  A truncated image can therefore make the driver read\nbeyond the firmware allocation during validation or loading.\n\nReplace the pointer-returning parser with bounded range helpers.  Validate\ntable entry sizes, descriptor indices, section ranges, the fixed\nbootloader load length, and the version tail before exposing any section.\nRead all file fields with unaligned little-endian accessors and assemble a\npartial final word from only the bytes that remain.  Apply the same range\nchecks to the legacy image before reading its fixed fields.","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: qlcnic: validate unified ROM sections before loading","id":"CVE-2026-90112","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"netdevsim: update queue NAPI association on queue reset","id":"CVE-2026-90113"},"packages":[],"prev":{"headline":"ip6mr: do not clone dst in ip6mr_cache_report()","id":"CVE-2026-90111"},"products":["Linux"],"published":"2026-09-17","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 local attacker can trigger integer overflows in the qlcnic driver ROM parser, causing out-of-bounds reads and potential system crashes or information leaks.","url":"https://insights.sbomify.com/CVE-2026-90112/"}