* [CVE-2026-97447][MODERATE REGULAR] ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() [ Upstream
@ 2026-09-24 19:09 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-09-24 19:09 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-97447
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() [ Upstream
Commit: e9a717b21caba155abe9d0c2102fe497536126b5
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e9a717b21caba155abe9d0c2102fe497536126b5
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97447
Analysis date: Thu, 24 Sep 2026 15:09:04 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
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-97447 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97447
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-97447 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-97447 CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:H';CWE-125;*CWE-20;CWE-1284;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'An out of bounds heap read can occur in the ACPICA LoadTable path because acpi_tb_find_table reads fixed size OEM ID and OEM Table ID fields while AML operands may contain shorter strings. A crafted AML table can cause the lookup code to read beyond the allocated string buffer, potentially causing a kernel fault or limited unintended memory disclosure. For the CVSS the PR:H value is used because reliable triggering normally requires control of firmware supplied AML, an ACPI table override, or another privileged platform configuration path. The issue is not directly network reachable. The base impact is limited because the patch shows an out of bounds read and does not demonstrate an overwrite or control flow primitive. The paranoid impact allows limited confidentiality impact and system availability impact from the memory safety violation, but does not claim privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) YES OOB DANGER DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH NO NO checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES
1. ActionableScore
* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* Final recommended bucket: **Ordinary Moderate**::
The patch establishes a bounded heap out of bounds read, but does not establish a user visible disclosure, a kernel write, a lifetime violation, a crash, or an authorization bypass. No score increase is justified for theoretical privilege escalation or information disclosure.
2. Signal breakdown
* +1 Concrete bounded out of bounds read. `acpi_tb_find_table()` expects fixed width OEM ID and OEM Table ID strings, while AML string operands can be shorter. The supplied patch explicitly prevents reads beyond the operand string storage by copying into fixed size zero terminated buffers.
* +0 No confidentiality point. The patch does not show that bytes read beyond the operand allocation are returned to userspace, sent over the network, or otherwise disclosed.
* +0 No integrity point. There is no demonstrated out of bounds write, controlled overwrite, refcount mutation, ownership violation, or authorization bypass.
* +0 No reliable kernel crash point. The supplied material does not demonstrate an Oops, panic, or reliable fault. A short fixed width overread may be tolerated by surrounding allocator storage.
* +0 No remote reachability point. The vulnerable AML execution path is not directly reachable from network traffic.
* +0 No local unprivileged trigger point. The evidence does not establish that an ordinary local user can install or execute attacker supplied ACPI AML.
* +0 No host admin penalty. Introducing attacker controlled AML commonly involves firmware control or ACPI table override mechanisms, but the complete privilege boundary is not fully established by the supplied patch alone.
* +0 No strong exploitation leverage. Controlled reclaim, arbitrary read or write, callback influence, type confusion, and privilege escalation are not demonstrated.
* +0 No repeated release or refcount mutation. This is not a UAF, double free, or stale lifetime operation.
3. Reachability analysis
The triggering input is an AML `LoadTable` operation with shorter than expected OEM ID or OEM Table ID strings. The relevant AML normally originates from platform firmware or an ACPI table override path.
A normal unprivileged local user is not shown to be able to supply such AML. ACPI table overrides generally require control of boot configuration, initramfs content, firmware, or another privileged platform-management path. However, the patch alone does not fully prove whether every affected deployment requires host-admin-equivalent privilege, so `HostAdminRequired=UNKNOWN` is more accurate than assuming `YES`.
There is no evidence that the complete trigger is namespace scoped. Containers, network namespaces, and delegated capabilities are not relevant to installing ACPI firmware tables. No direct remote trigger, ordinary packet path, special runtime device interface, or attacker controlled hardware DMA path is established.
4. Primitive and severity interpretation
The exact primitive is a limited heap out of bounds read in the ACPICA AML interpreter path. `acpi_tb_find_table()` may read fixed-size OEM fields from AML strings that are shorter than those fields. The patch changes the call site so that valid short strings are copied into fixed-size local buffers with explicit null termination.
This is not an active structured-object UAF, a stale reference, a repeated lifetime mutation, or a write primitive. It is also not demonstrated to be an information disclosure primitive because the bytes read are used for ACPI table matching and no read-back path is shown.
The appropriate classification is `CLASS_C`: invalid memory access with at most crash or DoS potential, but without an independently useful corruption primitive. The practical demonstrated consequence is malformed AML processing. A kernel fault is plausible in an instrumented build or at an allocation boundary, but is not established as reliable from the supplied evidence.
`ImportantCandidate=NO` because the patch does not establish meaningful exploitation leverage beyond the bounded read. `AutoDowngradeAllowed=YES` because no unresolved UAF, write, ownership violation, security-boundary bypass, or disclosure primitive remains.
5. One-sentence report phrase
A crafted ACPI AML LoadTable operation can cause ACPICA to read beyond a short OEM ID or OEM Table ID string, but the supplied patch establishes only a bounded out of bounds read with no demonstrated disclosure, write, privilege escalation, or direct remote trigger.
6. Manual review recommendation
MANUAL CHECK RECOMMENDED
The helper implementation of `acpi_tb_find_table()` and its exact comparison behavior should be checked to confirm the read width and whether any caller exposes compared memory or can make the overread reliably fault. Based on the supplied patch alone, this should not be treated as an Important-class memory corruption vulnerability.
7. Call-site confidence
Call-site confidence: medium
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() [ Upstream
Commit: e9a717b21caba155abe9d0c2102fe497536126b5
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e9a717b21caba155abe9d0c2102fe497536126b5
Changed files:
drivers/acpi/acpica/exconfig.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=e9a717b21caba155abe9d0c2102fe497536126b5
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-97447 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97447
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:H/UI:N/S:U/C:N/I:N/A:L
The Best / paranoid CVSS vector: AV:L/AC:H/PR:H/UI:N/S:U/C:L/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: 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 [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-24 19:09 21% [CVE-2026-97447][MODERATE REGULAR] ACPICA: Enhance OEM ID and Table ID validation in acpi_ex_load_table_op() [ 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