From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-98477][MODERATE REGULAR] perf/core: Fix NULL pmu_ctx passed to pmu->sched_task() Date: Sun, 18 Oct 2026 15:14:34 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-98477 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: 1 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: b5409311b606d536cc485f3706c242c2afa93edb List-Id: CVE: CVE-2026-98477 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: perf/core: Fix NULL pmu_ctx passed to pmu->sched_task() Commit: b5409311b606d536cc485f3706c242c2afa93edb Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b5409311b606d536cc485f3706c242c2afa93edb Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98477 Analysis date: Sun, 18 Oct 2026 15:14:34 -0400 ActionableScore: 1 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate Manual review required: NO Summary: A NULL PMU context passed to the ARM64 BRBE scheduling callback can cause a local kernel Oops or panic, but the affected path provides no UAF, writable corruption, disclosure, or authorization-bypass primitive. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98477 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98477 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-98477 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-98477 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=0 LEGACY=MODERATE RESULT=DIFF V39_AEGIS_ONE_STEP_UP=LOW->MODERATE TEMP_DISTANCE_MERGE_SKIP=AEGIS_NO_POSITIVE_SEVERITY_EVIDENCE (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC) 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-476;CWE-754;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 NULL pointer dereference can occur in the perf task scheduling path because __perf_pmu_sched_task() passes cpc.task_epc even though that context is NULL on this path. The ARM64 armv8pmu_sched_task() implementation reads the PMU from the supplied context, which can produce a kernel Oops or panic when BRBE support is active. For the CVSS the PR:L value is used for the paranoid score because some systems permit unprivileged perf_event_open access or delegate PMU access to restricted service or container accounts. Systems that restrict hardware performance events through perf_event_paranoid or capabilities normally require PR:H instead. The issue is local and is not directly network reachable. Impact is denial of service through a kernel crash. The analyzed path provides no UAF, OOB access, arbitrary write, or information disclosure primitive, so confidentiality and integrity remain unaffected. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 5.5 and the production ActionableScore returned 1 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 MODERATE because 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 V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 3.3 and ActionableScore 0 with primitive class CLASS_C and manual review NO. Its independently reconciled impact was MODERATE_KPANIC. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) 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 V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED - - guess ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=1 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 conservative score: 1 * Conservative score: 1 * Raw paranoid score: 1 * Paranoid score: 1 * No floor or cap was applied. * Final recommended bucket: **Ordinary Moderate**:: 2. Signal breakdown * +1 Reliable kernel crash or strong DoS. The supplied trace establishes a NULL dereference in `armv8pmu_sched_task()` and supports an Oops or panic when BRBE is active. * +0 Weak corruption concern. The callback only reads `pmu_ctx->pmu` through a NULL argument. No writable stale object or useful corruption sink is established. * No local-unprivileged bonus. `perf_event_open()` may be delegated on some systems, but the supplied evidence does not establish that an ordinary user can complete the BRBE-specific trigger. * No hardware penalty. BRBE is required, but the evidence does not establish that applicable ARM64 hardware is sufficiently rare to justify a numeric reduction. * No extra Availability point. It would duplicate the same NULL-dereference crash. * No UAF, OOB access, repeated release, attacker-controlled write, authorization bypass, disclosure, or integrity primitive is established. * B5-R does not apply because there is no retry-accumulated heap OOB write. * B3-PENDING does not apply because no shared-backing write exists. * B4-PENDING does not apply because no authorization decision changes from DENY to ALLOW. 3. Reachability analysis The vulnerable operation executes in the local perf task-scheduling path. ARM64 BRBE support and an applicable PMU scheduling context are prerequisites. The supplied material does not resolve whether the complete trigger requires a privileged performance-monitoring configuration or can be reached by a user permitted to create relevant perf events. No network trigger, namespace-scoped capability chain, or remote interface is established. No race or narrow timing window is required once the affected callback is reached. `HostAdminRequired` and `RequiresHostUID0` remain UNKNOWN because the complete event-creation and BRBE-activation path is not shown. 4. Primitive and severity interpretation The exact primitive is a NULL pointer read caused by passing `cpc->task_epc` to `pmu->sched_task()` when that pointer is NULL. `armv8pmu_sched_task()` dereferences the argument to read its `pmu` member, producing an immediate fault. This is CLASS_C invalid-state and crash behavior. It is not a UAF, stale-object lifetime violation, OOB operation, or active structured-state corruption. The demonstrated consequence is local kernel Oops or panic. There is no patch-supported consequence beyond denial of service and no unresolved Important-grade primitive. `ImportantCandidate=NO` because neither memory corruption nor a security-boundary violation is present. `AutoDowngradeAllowed=YES` because the root cause and consequence are constrained to an invalid NULL context dereference. 5. One-sentence report phrase A NULL PMU context passed to the ARM64 BRBE scheduling callback can cause a local kernel Oops or panic, but the affected path provides no UAF, writable corruption, disclosure, or authorization-bypass primitive. 6. Manual review recommendation NO MANUAL CHECK NEEDED The patch establishes a direct crash-only NULL dereference, and none of the B5-R, B3-PENDING, B4-PENDING, lifetime-corruption, or trust-boundary preservation conditions apply. 7. Call-site confidence Call-site confidence: high ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: perf/core: Fix NULL pmu_ctx passed to pmu->sched_task() Commit: b5409311b606d536cc485f3706c242c2afa93edb Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b5409311b606d536cc485f3706c242c2afa93edb Commit description: perf_pmu_sched_task() returns early when cpuctx->task_ctx is set, and cpc->task_epc is only non-NULL while a task context is scheduled in on this CPU. __perf_pmu_sched_task() therefore always passes NULL: Unable to handle kernel NULL pointer dereference at virtual address 00 pc : armv8pmu_sched_task+0x14/0x50 Call trace: armv8pmu_sched_task+0x14/0x50 (P) perf_pmu_sched_task+0xac/0x108 __perf_event_task_sched_out+0x6c/0xe0 Pass &cpc->epc instead, the CPU-wide context for this PMU, which the function already dereferences a few lines up to find pmu. armv8pmu_sched_task() is the only in-tree implementation that dereferences the argument, and it only reads ->pmu, so the oops needs BRBE, added in v6.17. Fixes: bd27568 ("perf: Rewrite core context handling") Signed-off-by: Puranjay Mohan Signed-off-by: Peter Zijlstra (Intel) Tested-by: Yifan Wu Cc: stable@vger.kernel.org Link: https://patch.msgid.link/20260810133540.1947118-2-puranjay@kernel.org Signed-off-by: Greg Kroah-Hartman Changed files: kernel/events/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=b5409311b606d536cc485f3706c242c2afa93edb ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-98477 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98477 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: unknown Paranoid ActionableScore: 1 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).