{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98665 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98665 is a vulnerability in Linux, published on 18 Oct 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-98665 and fix it if it is affected.\n\nWhat it is: CVE-2026-98665 is a vulnerability in Linux, published on 18 Oct 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-98665 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-98665/ (Markdown: https://insights.sbomify.com/CVE-2026-98665/index.md)","id":"CVE-2026-98665","markdown":"https://insights.sbomify.com/CVE-2026-98665/index.md","name":"CVE-2026-98665","record":{"aliases":["AZL-108957","BELL-CVE-2026-98665","DEBIAN-CVE-2026-98665","GHSA-g7xj-pf5g-99j9","UBUNTU-CVE-2026-98665"],"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 Linux kernel max30102 driver can cause a system crash when an interrupt occurs without an active buffer.","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\niio: health: max30102: fix NULL dereference in interrupt handler\n\nThe interrupt is requested in max30102_probe() and stays enabled\nfor the lifetime of the device, but indio_dev-\u003eactive_scan_mask is only\nvalid while a buffer is enabled. When an interrupt arrives while no\nbuffer is enabled, the handler dereferences the NULL active_scan_mask:\n\n  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n  Call trace:\n   __bitmap_weight+0x64/0x98 (P)\n   max30102_interrupt_handler+0x48/0x160 [max30102]\n\nCall max30102_fifo_count() at the top of the handler and return early\nunless it reports a FIFO sample is ready. Because FIFO_RDY is the only\ninterrupt source enabled in max30102_chip_init(), an invocation of\nmax30102_interrupt_handler() without the FIFO_RDY interrupt status bit\nset carries no data to read and can return before touching\nactive_scan_mask. A negative return from max30102_fifo_count()\nindicates a failed interrupt status read and is treated the same way.","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":"iio: health: max30102: fix NULL dereference in interrupt handler","id":"CVE-2026-98665","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":"iio: gyro: adis16136: fix unprotected debugfs reads","id":"CVE-2026-98666"},"packages":[],"prev":{"headline":"iio: imu: adis16400: fix unprotected debugfs reads","id":"CVE-2026-98664"},"products":["Linux"],"published":"2026-10-18","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 Linux kernel max30102 driver can cause a system crash when an interrupt occurs without an active buffer.","url":"https://insights.sbomify.com/CVE-2026-98665/"}