From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98660][MODERATE REGULAR] iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup Date: Sat, 24 Oct 2026 03:46:05 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98660 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 9db6684fab228edd3b8861a172ccbce3236f027a List-Id: CVE: CVE-2026-98660 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup Commit: 9db6684fab228edd3b8861a172ccbce3236f027a Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9db6684fab228edd3b8861a172ccbce3236f027a Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98660 Analysis date: Sat, 24 Oct 2026 03:46:05 -0400 ActionableScore: 2 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: A flattened-element count used as a two-column row count permits an internal sampling-frequency table OOB read with possible kernel fault but no shown disclosure or write. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98660 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98660 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: MODERATE REGULAR 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-98660 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-98660 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE AEGIS_AS=1 LEGACY=MODERATE RESULT=SAME (final reconciliation agrees; DECISION: both MODERATE) Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';CWE-125;CWE-129;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.4';DESCR 'The BMP280 sampling frequency lookup treated the flattened number of integer elements as the number of two element rows. The loop could therefore read avail entries beyond the end of the sampling frequency table when processing an unsupported or sufficiently late frequency value. For the CVSS the PR:H value is selected because changing this IIO configuration normally requires privileged write access to the device sysfs attributes. The demonstrated primitive is an out of bounds read with no direct return of adjacent memory and no evidence of an out of bounds write or UAF. Availability impact is normally limited, although a kernel fault remains a plausible worst case if the invalid read crosses inaccessible memory. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.4 and the production ActionableScore returned 2 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. 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. 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. The shadow agreed with the final production impact and aggregation did not change that impact. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2) MAYBE OOB SIMPLEFIX LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 PrimitiveClass=CLASS_C RealUAF=NO HostAdminRequired=UNKNOWN NamespaceScopedPrivilege=UNKNOWN ImportantCandidate=NO ManualReview=RECOMMENDED AutoDowngradeAllowed=YES RequiresHostUID0=UNKNOWN AuthorizationDecisionBypass=NO ProtectedResourceImpact=NONE B4PendingReview=NO B4PendingConfirmed=NO 1. ActionableScore * Raw base score: 2. * Conservative score: 2; no floor or cap applied. * Raw paranoid score: 2. * Paranoid score: 2; no distinct stronger primitive supports an additional point. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 weak/indirect corruption candidate: `num_sampling_freq_avail` counts flattened integers but was used as the row bound for `avail[i][0..1]`, permitting an out-of-bounds kernel read. * +1 plausible kernel fault/DoS: sufficiently late lookup iterations may read into inaccessible memory. A panic is possible, not demonstrated or guaranteed. * No OOB-write points: the shown operation only reads the frequency table. * No confidentiality point: adjacent bytes are not returned to userspace or another observable sink. * No integrity point, UAF, controlled reclaim, retry-accumulated write, or authorization bypass is shown. * NEW52/B5-R does not apply: there is no write, retry-accumulated index, or later consumption of corrupted structured state. * No extra availability point: it would duplicate the same possible fault. 3. Reachability analysis The vulnerable lookup is reached through an IIO sampling-frequency write using an unsupported or sufficiently late value. The supplied summary says this sysfs configuration normally requires privileged device-attribute access, but the exact permissions, delegation, and capability namespace are not shown. Therefore host-admin, UID 0, and namespace-scoped privilege requirements remain unknown. There is no race, retry sequence, special hardware timing, or prior configuration chain established beyond presence of the supported BMP280-family device. 4. Primitive and severity reading The exact primitive is an array-bound mismatch causing a read beyond a static sampling-frequency table. It is not active-state corruption, an OOB write, or a lifetime violation. The shown consequence is incorrect internal comparison data; a kernel fault is plausible if the read crosses an inaccessible boundary. Disclosure, state modification, and privilege escalation are unsupported. This is CLASS_C, not an Important candidate, and automatic Moderate handling remains permissible. 5. One-sentence report phrase A flattened-element count used as a two-column row count permits an internal sampling-frequency table OOB read with possible kernel fault but no shown disclosure or write. 6. Manual review advice MANUAL CHECK RECOMMENDED Confirm the affected sysfs attribute permissions and whether the invalid read can reliably cross into inaccessible memory. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: iio: pressure: bmp280: fix out-of-bounds access in sampling frequency lookup Commit: 9db6684fab228edd3b8861a172ccbce3236f027a Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9db6684fab228edd3b8861a172ccbce3236f027a Commit description: The sampling frequency tables store each frequency as an integer part and a fractional part in micro units. num_sampling_freq_avail is initialized to the number of flattened integer elements because read_avail() returns the table as a flat array. bmp280_write_sampling_frequency(), however, indexes the same table as a two-dimensional array and uses num_sampling_freq_avail as the number of rows. Convert the flattened element count back to the number of rows before iterating over the table. Fixes: 10b40ff ("iio: pressure: bmp280: Add more tunable config parameters for BMP380") Cc: stable@vger.kernel.org Signed-off-by: Hui Su Reviewed-by: Joshua Crofts Signed-off-by: Jonathan Cameron Signed-off-by: Greg Kroah-Hartman Changed files: drivers/iio/pressure/bmp280-core.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=9db6684fab228edd3b8861a172ccbce3236f027a ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98660 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98660 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: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.4 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: 2 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: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR 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).