* [CVE-2026-92524][LOW] irqchip/gic-v3-its: Prevent leak in its_vpe_irq_domain_alloc() [ Upstream
@ 2026-09-18 6:04 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-09-18 6:04 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-92524
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: irqchip/gic-v3-its: Prevent leak in its_vpe_irq_domain_alloc() [ Upstream
Commit: 82bccf7f9a12bf0eec9774968f6a853020ea26d3
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=82bccf7f9a12bf0eec9774968f6a853020ea26d3
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-92524
Analysis date: Fri, 18 Sep 2026 02:04:38 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate
Manual review required: NO
Summary:
No one-sentence report phrase was found.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2026-92524 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-92524
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-92524 LOW https://www.kernelcve.org/list/?q=CVE-2026-92524 CHECK WITH IMPACT FROM ORIG NN LOW 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-772;*CWE-401;CWE-404;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'A resource leak can occur in the GICv3 ITS VPE irq domain allocation error path because its_vpe_teardown is not called when its_irq_gic_domain_alloc fails after VPE resources have already been initialized. This can leave ITS VPE related resources allocated after a failed VM interrupt setup operation and may accumulate across repeated failed allocations. For the CVSS the PR:L is used because practical triggering requires local access to the virtualization control plane such as KVM ioctls or an equivalent service account, not full host administrator privileges in all deployments. AC:H is used because the vulnerable path depends on an allocation failure or lower irq domain failure during setup. The issue is not network reachable and has no clear memory corruption primitive. Impact is denial of service through resource exhaustion only.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2) YES INIT SIMPLEFIX LEAK ERRORPATH LINUS NO NO checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=2
ActionableScoreLower=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
### 1. ActionableScore
* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 2
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate**::
No floor or cap was applied. The conservative score reflects a concrete resource leak only. The paranoid score adds limited weight for repeated failed allocations accumulating leaked ITS VPE resources, but there is no memory corruption, UAF, repeated release/refcount mutation, authorization bypass, or demonstrated privilege escalation.
### 2. Signal breakdown
Positive signals:
* +1 Concrete persistent kernel resource/reference leak. The patch directly shows that `its_vpe_teardown()` was not called when `its_irq_gic_domain_alloc()` failed, leaving already initialized VPE resources unreleased.
* +1 paranoid only for possible sustained resource exhaustion. Repeated failed VPE IRQ domain allocations may accumulate leaked ITS/VPE resources and eventually cause availability impact.
Negative or non-awarded signals:
* Real UAF not awarded. No stale post-lifetime dereference or use-after-free is established.
* Concrete repeated release/refcount not awarded. The bug is a missing teardown/release, not a second release through a dangling reference.
* Strong LPE or strong exploitation leverage not awarded. No controlled reclaim, arbitrary write, refcount takeover, callback control, or object replacement is shown.
* Confidentiality and integrity not awarded. The patch supports only resource leakage and possible availability impact.
* Reliable kernel crash not awarded. The patch describes a leak, not an immediate panic or Oops.
* Remote reachability not awarded. The path is virtualization/interrupt allocation control plane, not packet or network input.
* Hardware rarity penalty not applied. The code is hardware/platform specific, but the evidence does not prove rare physical-only attacker requirements beyond the relevant virtualization platform.
Concrete repeated-release/refcount checklist:
* First release can end lifetime: not applicable.
* Exact same reference survives: not established.
* Second lifetime/refcount mutation: not present.
* +1 Concrete repeated release/refcount awarded: no.
* Paranoid repeated-refcount leverage awarded: no.
* FLOOR 5 applied: no.
### 3. Reachability analysis
The likely trigger is local access to a virtualization control plane that can create or initialize VM interrupt/VPE state on ARM systems using GICv3 ITS or related VPE support. This may be reachable by a VMM process, KVM-using service account, or delegated virtualization service, so full host administrator privilege is not positively required in all deployments.
The complete trigger still depends on an allocation failure or lower IRQ domain allocation failure during setup. That makes the path less directly controllable than a normal syscall crash. Namespace-scoped privilege is not established, and this is not a network-reachable vulnerability.
Prior host setup is required in the practical sense that the affected hardware/platform and virtualization stack must be present and used, but this does not convert the issue into a strong security-boundary primitive.
### 4. Primitive and severity interpretation
The exact primitive is a missing cleanup/teardown call in an error path, causing a persistent leak of ITS VPE related resources. This is a resource-management defect, not memory corruption.
The affected object is kernel-managed interrupt virtualization state, but the stale-use pattern required for UAF is not present. The demonstrated consequence is potential resource exhaustion after repeated failed allocations. The speculative consequence is broader DoS if leaked resources accumulate enough to disrupt VM interrupt setup or related host resources.
PrimitiveClass is CLASS_C because the issue is primarily DoS/resource exhaustion without an independently useful corruption primitive. ImportantCandidate is NO because there is no UAF, no repeated lifetime mutation, no controlled corruption, and no boundary bypass. AutoDowngradeAllowed is YES because automatic downgrade would not discard a meaningful unresolved exploitation primitive.
Likely operational severity is Low to ordinary Moderate.
### 5. One-sentence report phrase
A missing VPE teardown call in the GICv3 ITS allocation error path can leak interrupt virtualization resources after failed setup attempts, causing only potential local resource-exhaustion DoS without evidence of memory corruption or privilege escalation.
### 6. Manual review recommendation
NO MANUAL CHECK NEEDED
Reason: this is a concrete but constrained resource leak with no UAF, no repeated release/refcount mutation, no network reachability, and no plausible Important-grade exploitation primitive in the supplied evidence.
### 7. Call-site confidence
Call-site confidence: high
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: irqchip/gic-v3-its: Prevent leak in its_vpe_irq_domain_alloc() [ Upstream
Commit: 82bccf7f9a12bf0eec9774968f6a853020ea26d3
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=82bccf7f9a12bf0eec9774968f6a853020ea26d3
Changed files:
drivers/irqchip/irq-gic-v3-its.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=82bccf7f9a12bf0eec9774968f6a853020ea26d3
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-92524 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-92524
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:H/PR:L/UI:N/S:U/C:N/I:N/A:L
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: 1
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: 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 [email protected] (and both
send reply to CVE record itself too and see "reply" button below for howto reply).
^ permalink raw reply [relevance 21%]
Results 1-1 of 1 | reverse | sort options + mbox downloads above
-- links below jump to the message on this page --
2026-09-18 6:04 21% [CVE-2026-92524][LOW] irqchip/gic-v3-its: Prevent leak in its_vpe_irq_domain_alloc() [ Upstream AL-KERNEL
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox