From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-72369][MODERATE REGULAR] minix: avoid overflow in bitmap block count calculation [ Upstream Date: Sun, 16 Aug 2026 05:15:27 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-72369 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: 4 X-AL-KERNEL-ActionableScore-Lower: 1 X-AL-KERNEL-Commit: a11ebaab50d27d6c4c78506f84ff36452e0b901d List-Id: CVE: CVE-2026-72369 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: minix: avoid overflow in bitmap block count calculation [ Upstream Commit: a11ebaab50d27d6c4c78506f84ff36452e0b901d Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a11ebaab50d27d6c4c78506f84ff36452e0b901d Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72369 Analysis date: Sun, 16 Aug 2026 05:15:27 -0400 ActionableScore: 4 ActionableScore lower bound: 1 Actionable bucket: Borderline manual review recommended / Ordinary Moderate otherwise Manual review required: YES Summary: A crafted Minix v3 filesystem image can trigger an unsigned integer overflow in bitmap block count validation, causing zero imap or zmap block counts to be accepted and leading to a NULL pointer dereference and kernel panic during mount. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72369 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72369 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: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-72369 MODERATE CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-190;*CWE-20;**CWE-476;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.5';DESCR 'A crafted Minix v3 filesystem image can make minix_blocks_needed() overflow while calculating the required imap or zmap bitmap block count. The wrapped result can make a zero bitmap block count look valid, so minix_fill_super() may later dereference s_imap(0) or s_zmap(0) even though no bitmap buffers were allocated. For the CVSS the PR:L is used for the paranoid score because some environments delegate mount operations to container root, mount helpers, user namespace based setups, or local automount policy instead of requiring full host root. The issue is not network reachable by itself and requires the crafted filesystem image to be mounted locally. Impact is denial of service through kernel panic. No concrete primitive for information disclosure or privilege escalation is visible from the patch context.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended / Ordinary Moderate otherwise (with actual score 3) SKIP CVE-2026-72369 UNKNOWN SKIP No affected files built, so skip this CVE NO - - unknown MAYBE DANGER DISK LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=4 ActionableScoreLower=1 ## 1. ActionableScore * Conservative score: 1 * Paranoid score: 4 * Final recommended bucket: **Borderline manual review recommended / Ordinary Moderate otherwise**:: ## 2. Signal breakdown Conservative signals: * Reliable kernel crash / strong DoS: +1 The commit explicitly says mounting a crafted Minix v3 image can dereference `s_imap[0]` or `s_zmap[0]` when no bitmap buffers were allocated, causing kernel panic. * Availability impact realistic: +1 The described impact is a host kernel panic during mount, not just a warning or recoverable error. * Important filesystem/storage path: +1 The bug is in filesystem superblock validation and mount-time metadata parsing. * Requires admin/root/CAP_SYS_ADMIN in typical deployments: -2 Mounting arbitrary filesystem images normally requires administrative privileges. Paranoid additional interpretation: * Local unprivileged trigger: +1 In some environments, mount operations may be delegated through container root, mount helpers, user namespace based setups, removable media automount policy, or desktop automounters. Not awarded: * No generic memory corruption bonus. The demonstrated primitive is NULL pointer dereference after integer overflow validation bypass, not UAF, OOB write, double free, arbitrary write, or type confusion. * No privilege escalation plausible bonus. The patch context supports kernel panic, but not attacker-controlled reclaim, write primitive, object confusion, or privilege boundary takeover. * No confidentiality or integrity impact. There is no supported read disclosure or unauthorized write primitive. Call-site confidence: high. The commit describes the downstream call path from `minix_check_superblock()` to `minix_fill_super()` and the concrete dereference target. ## 3. Reachability analysis The realistic trigger is local mounting of a crafted Minix v3 filesystem image with `s_ninodes` or `s_zones` near `UINT_MAX`. In standard deployments this requires `CAP_SYS_ADMIN`, so the conservative score is low. Namespaces, container root, mount helpers, or automount policies can lower the practical privilege requirement, but that is environment-dependent. The issue is not network reachable by itself. Minix is not a broad default filesystem in most production environments, but the vulnerable parser is reachable if Minix filesystem support is available and an attacker can get the crafted image mounted. ## 4. Severity interpretation This behaves like an ordinary Moderate in typical server deployments because it is a local crafted-filesystem DoS requiring mount privilege. It becomes borderline actionable when delegated or automated mounting is in scope, because a low-privileged local actor may be able to turn a crafted image into a kernel panic. Theoretical memory corruption potential is weak here. The realistic evidence supports NULL pointer dereference and availability impact only. ## 5. One-sentence report phrase A crafted Minix v3 filesystem image can trigger an unsigned integer overflow in bitmap block count validation, causing zero imap or zmap block counts to be accepted and leading to a NULL pointer dereference and kernel panic during mount. ## 6. Manual review recommendation MANUAL CHECK RECOMMENDED Reason: the core primitive is DoS-only, but crafted filesystem parser bugs depend heavily on local mount policy, container delegation, and automount behavior. It should not be treated as Important by default, but should be reviewed before auto-closing in products where untrusted users can influence mounts. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: minix: avoid overflow in bitmap block count calculation [ Upstream Commit: a11ebaab50d27d6c4c78506f84ff36452e0b901d Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a11ebaab50d27d6c4c78506f84ff36452e0b901d Changed files: fs/minix/minix.h 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=a11ebaab50d27d6c4c78506f84ff36452e0b901d ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72369 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72369 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:H The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.5 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: 1 Paranoid ActionableScore: 4 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).