From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98665][LOW] iio: health: max30102: fix NULL dereference in interrupt handler Date: Sat, 24 Oct 2026 06:22:39 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98665 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 0 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: eeb23ba97bd8016e815ef70300b8d34a0a316b90 List-Id: CVE: CVE-2026-98665 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: iio: health: max30102: fix NULL dereference in interrupt handler Commit: eeb23ba97bd8016e815ef70300b8d34a0a316b90 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=eeb23ba97bd8016e815ef70300b8d34a0a316b90 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98665 Analysis date: Sat, 24 Oct 2026 06:22:39 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: A MAX30102/MAX30105 interrupt arriving while its IIO buffer is disabled can dereference a NULL scan mask and crash the kernel on affected hardware. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98665 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98665 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-98665 LOW https://www.kernelcve.org/list/?q=CVE-2026-98665 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=LOW RESULT=DIFF TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (final Legacy and Aegis differ; FINAL: LOW, Aegis: MODERATE_KPANIC) Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;*CWE-20;CWE-754;BEST CVSS score: '4.7';DESCR 'The max30102 interrupt handler can run while the IIO buffer is disabled even though active_scan_mask is only valid while that buffer is enabled. The handler previously passed the NULL mask to bitmap_weight before checking whether FIFO data was ready, causing a kernel NULL pointer dereference and potentially a host crash. For the CVSS the PR:L value reflects that reliable triggering normally requires local access to IIO buffer control or influence over a process managing the sensor. AC:H reflects the required device state and interrupt timing. The issue is not network reachable and requires supported MAX30102 or MAX30105 hardware. The demonstrated primitive is a NULL dereference with availability impact only and no supported confidentiality or integrity impact. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.7 and the production ActionableScore returned 0 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE to LOW because the ActionableScore threshold rule was applied. final reconciliation stage LOW to LOW because KP specialist did not establish a qualifying panic and the cross model evidence reconciliation rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH and DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 and KPANIC_UNSUPPORTED_REMOVED and V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED. The independent weaker Aegis shadow evaluated CVSS 2.2 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE_KPANIC. The models disagreed but the aggregation rules retained the production result. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0) MAYBE OOB NULLPTR SIMPLEFIX HARDWARE LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 KPANIC_UNSUPPORTED_REMOVED V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=NO AutoDowngradeAllowed=YES RequiresHostUID0=UNKNOWN AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw base score: -2. * Conservative score: 0 after applying the score-range lower bound. * Raw paranoid score: -2. * Paranoid score: 0 after applying the score-range lower bound. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Reliable kernel crash/strong DoS: `bitmap_weight()` receives a NULL `active_scan_mask`, with an observed kernel NULL-pointer fault. * -1 Hard/special timing: triggering requires an interrupt while the IIO buffer is disabled and no FIFO-ready sample exists; reliable attacker control of this ordering is not shown. * -2 Rare hardware dependency: the vulnerable handler requires supported MAX30102/MAX30105 sensor hardware. * No local-unprivileged bonus: local buffer control or influence over a sensor-management process is suggested, but the complete trigger and permissions are not established. * No memory-corruption, UAF, write, disclosure, integrity, authorization, or protected-resource signal is shown. * No extra availability point: it would duplicate the same NULL-dereference crash. 3. Reachability analysis The path requires the specific sensor, its enabled IRQ, and an interrupt during the buffer-disabled state. The evidence does not establish whether an ordinary user, delegated service, or host administrator can reliably induce the complete sequence. No namespace capability, prior device assignment, or network reachability is shown. The timing appears specialized and is not shown repeatable under attacker control. 4. Primitive and severity reading The exact primitive is a NULL-pointer read passed into bitmap processing, producing a fault before useful corrupted state is consumed. It is neither an active-object lifetime violation nor a write primitive. The demonstrated effect is availability loss; confidentiality, integrity, authorization bypass, and privilege escalation are unsupported. This is CLASS_C, not a NEW52 retry-accumulated OOB write, NEW53 shared-backing write, or B4 authorization candidate. Auto-downgrade is allowed because no unresolved corruption or trust-boundary primitive remains. 5. One-sentence report phrase A MAX30102/MAX30105 interrupt arriving while its IIO buffer is disabled can dereference a NULL scan mask and crash the kernel on affected hardware. 6. Manual review advice NO MANUAL CHECK NEEDED The patch and trace establish a constrained hardware-dependent NULL dereference with availability impact only. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: iio: health: max30102: fix NULL dereference in interrupt handler Commit: eeb23ba97bd8016e815ef70300b8d34a0a316b90 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=eeb23ba97bd8016e815ef70300b8d34a0a316b90 Commit description: The interrupt is requested in max30102_probe() and stays enabled for the lifetime of the device, but indio_dev->active_scan_mask is only valid while a buffer is enabled. When an interrupt arrives while no buffer is enabled, the handler dereferences the NULL active_scan_mask: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 Call trace: __bitmap_weight+0x64/0x98 (P) max30102_interrupt_handler+0x48/0x160 [max30102] Call max30102_fifo_count() at the top of the handler and return early unless it reports a FIFO sample is ready. Because FIFO_RDY is the only interrupt source enabled in max30102_chip_init(), an invocation of max30102_interrupt_handler() without the FIFO_RDY interrupt status bit set carries no data to read and can return before touching active_scan_mask. A negative return from max30102_fifo_count() indicates a failed interrupt status read and is treated the same way. Fixes: 90579b6 ("iio: health: max30102: Add MAX30105 support") Suggested-by: Jonathan Cameron Signed-off-by: Marco Chen Cc: Signed-off-by: Jonathan Cameron Signed-off-by: Greg Kroah-Hartman Changed files: drivers/iio/health/max30102.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=eeb23ba97bd8016e815ef70300b8d34a0a316b90 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98665 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98665 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: Not available The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.7 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: unknown Paranoid ActionableScore: 0 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).