{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97537 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97537 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-97537 and fix it if it is affected.\n\nWhat it is: CVE-2026-97537 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-97537 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-97537/ (Markdown: https://insights.sbomify.com/CVE-2026-97537/index.md)","id":"CVE-2026-97537","markdown":"https://insights.sbomify.com/CVE-2026-97537/index.md","name":"CVE-2026-97537","record":{"aliases":["AZL-104723","BELL-CVE-2026-97537","DEBIAN-CVE-2026-97537","GHSA-46xm-fghf-r34f","UBUNTU-CVE-2026-97537"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A NULL pointer dereference in the qla2xxx SCSI driver during queue teardown can cause a kernel panic, leading to denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nscsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking\n\nqla25xx_free_req_que() and qla25xx_free_rsp_que() have two pre-existing\nbugs exposed on the error path of qla25xx_create_{req,rsp}_que():\n\n 1. When dma_alloc_coherent() fails during queue creation, the error\n    path calls the free function with req-\u003ering / rsp-\u003ering still NULL\n    (from kzalloc).  The unconditional dma_free_coherent() with a NULL\n    cpu_addr is undefined behavior and can panic.\n\n 2. The free functions clear req_qid_map / rsp_qid_map under vport_lock,\n    but the create functions protect the same bitmaps with mq_lock.\n    This provides no mutual exclusion.  Additionally, the create error\n    path clears the bit and releases mq_lock before calling the free\n    function, creating a window where another thread can allocate the\n    same que_id and have its ha-\u003ereq_q_map entry clobbered by the\n    subsequent lockless NULL assignment in the free function.\n\nFix by:\n\n - Guarding dma_free_coherent() with a NULL check on the ring pointer.\n\n - Using mq_lock (the lock held by all creators) in the free functions\n   to atomically NULL the map entry and clear the bitmap bit.\n\n - Removing the now-redundant clear_bit blocks from the create error\n   paths since the free functions handle it atomically.","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":"scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking","id":"CVE-2026-97537","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"hwmon: (asus_rog_ryujin) Validate HID report lengths","id":"CVE-2026-97538"},"packages":[],"prev":{"headline":"scsi: qla2xxx: Fix use-after-free of qpair work on queue teardown","id":"CVE-2026-97536"},"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 NULL pointer dereference in the qla2xxx SCSI driver during queue teardown can cause a kernel panic, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-97537/"}