From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-99250][LOW] printk: Postpone kthread startup [ Upstream Date: Tue, 03 Nov 2026 22:04:18 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-99250 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: a86bcdd84c8fe7a45f73e12d53fe06fea07d1ceb List-Id: CVE: CVE-2026-99250 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: printk: Postpone kthread startup [ Upstream Commit: a86bcdd84c8fe7a45f73e12d53fe06fea07d1ceb Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a86bcdd84c8fe7a45f73e12d53fe06fea07d1ceb Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99250 Analysis date: Tue, 03 Nov 2026 22:04:18 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: Early NBCON printer-thread startup can interfere with SMP initialization and hang affected systems during boot, without a demonstrated runtime attacker path or corruption primitive. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-99250 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99250 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-99250 LOW https://www.kernelcve.org/list/?q=CVE-2026-99250 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT LOW AEGIS_AS=0 LEGACY=LOW RESULT=SAME (final reconciliation agrees; DECISION: both LOW) Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';CWE-362;CWE-696;BEST CVSS score: '4.1';DESCR 'NBCON printer kthreads were started during early boot and could asynchronously change interrupt state while SMP initialization was still in progress. On affected hardware this may contribute to missed IPIs and leave the system hanging during boot. For the CVSS the PR:H value reflects that a potential attacker would need control over boot or kernel configuration and a reboot because no unprivileged runtime trigger is established. The demonstrated impact is availability loss only. There is no evidence of UAF, OOB access, information disclosure, or another memory corruption primitive. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 4.1 and the production ActionableScore returned 0 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. No severity changing production threshold or specialist override was recorded. 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. The independent weaker Aegis shadow evaluated CVSS 4.1 and ActionableScore 0 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was LOW. The shadow agreed with the final production impact and aggregation did not change that impact. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0) MAYBE INIT SIMPLEFIX LEAK HARDWARE LINUS - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 PrimitiveClass=NONE RealUAF=NO HostAdminRequired=YES NamespaceScopedPrivilege=NO 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 clamping the negative raw score. * Raw paranoid score: -2. * Paranoid score: 0 after clamping. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Reliable strong DoS: affected SMP systems can reproducibly hang during boot. * -2 Full host-administrator-equivalent prerequisite: the supplied evidence establishes no runtime attacker interface; an intentional trigger would require control of boot/kernel configuration and reboot. * -1 Hard platform-dependent timing: the failure depends on early asynchronous interrupt-state changes interfering with SMP setup and occurs only on affected hardware/timing. * No memory-corruption signal: the patch only moves `printk_set_kthreads_ready()` from `early_initcall` to `subsys_initcall`. * No UAF, OOB access, attacker-controlled write, authorization bypass, confidentiality impact, integrity impact, or separate availability effect is shown. * No B5-R retry-accumulated OOB or B3 shared-backing write mechanics exist. 3. Reachability analysis There is no attacker-invocable runtime operation. The issue arises during global early boot before namespace-scoped operation is relevant. An adversarial trigger would require effective control over host boot or kernel configuration plus a reboot. Numeric host UID 0 is not specifically established, but effective host-administrator control is required. No special device is required, although reproduction is hardware/platform dependent. 4. Primitive and severity reading The demonstrated defect is initialization ordering: NBCON printer kthreads can asynchronously alter interrupt state before SMP initialization completes, plausibly causing missed IPIs and a boot hang. This is not memory corruption or corrupted structured-state consumption. The shown impact is availability loss only, with no useful primitive beyond the hang. `PrimitiveClass=NONE`, so there is no Important-preserving ambiguity and automatic downgrade is allowed. 5. One-sentence report phrase Early NBCON printer-thread startup can interfere with SMP initialization and hang affected systems during boot, without a demonstrated runtime attacker path or corruption primitive. 6. Manual review advice NO MANUAL CHECK NEEDED The patch and supplied evidence support only a host-controlled, timing-dependent boot availability failure. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: printk: Postpone kthread startup [ Upstream Commit: a86bcdd84c8fe7a45f73e12d53fe06fea07d1ceb Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a86bcdd84c8fe7a45f73e12d53fe06fea07d1ceb Changed files: kernel/printk/printk.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=a86bcdd84c8fe7a45f73e12d53fe06fea07d1ceb ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-99250 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-99250 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:H/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.1 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).