* [CVE-2026-80747][MODERATE REGULAR] drm/amdkfd: Add bounds check for CRAT subtype length [ Upstream
@ 2026-09-03 9:30 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-09-03 9:30 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-80747
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: drm/amdkfd: Add bounds check for CRAT subtype length [ Upstream
Commit: ca91e0cc8087568e4b791648a7c01e804f48cb73
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ca91e0cc8087568e4b791648a7c01e804f48cb73
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80747
Analysis date: Thu, 03 Sep 2026 05:30:37 -0400
ActionableScore: 3
ActionableScore lower bound: 1
Actionable bucket: Borderline manual review recommended
Manual review required: YES
Summary:
No one-sentence report phrase was found.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2026-80747 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80747
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-80747 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-80747 CHECK WITH IMPACT FROM ORIG NN LOW Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H';CWE-125;*CWE-20;CWE-130;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.1';DESCR 'The amdkfd CRAT parser can read beyond the supplied CRAT image because it validates that the subtype header is present but does not validate that the advertised subtype length also stays inside the image boundary. A malformed CRAT table with an oversized length can make kfd_parse_subtype read fields from memory outside the CRAT image after casting the subtype header to a specific structure. For the CVSS the PR:H is used because reliable attacker control over CRAT platform data normally requires administrative firmware boot or hypervisor level control rather than ordinary local user access. The issue is not network reachable. Impact is primarily denial of service or driver initialization failure, with a conservative worst case of limited confidentiality impact from an out of bounds kernel read and high availability impact if the read faults or corrupts parser decisions.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline manual review recommended (with actual score 2) SKIP CVE-2026-80747 UNKNOWN SKIP No affected files built, so skip this CVE NO - - unknown MAYBE OOB SIMPLEFIX HARDWARE DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH - - checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=3
ActionableScoreLower=1
1. ActionableScore
* Conservative score: 1
* Paranoid score: 3
* Final recommended bucket: **Borderline manual review recommended**::
2. Signal breakdown
* Firmware-mediated external influence: +1. The malformed CRAT data is platform or firmware supplied, not ordinary packet or syscall input.
* Weak limited OOB read candidate: +1 in paranoid scoring. The patch prevents kfd_parse_subtype() from reading past crat_image after trusting sub_type_hdr->length.
* Reliable kernel crash / strong DoS: +1 in paranoid scoring. An OOB read in kernel driver initialization/parsing can plausibly fault or break amdkfd initialization, but no write primitive is shown.
* Confidentiality impact plausible: +1 in paranoid scoring. Limited kernel OOB read can theoretically expose adjacent data through parser effects or logs, but no direct leak path is demonstrated.
* Requires admin/firmware/hypervisor control in typical deployments: -2. Ordinary local users normally cannot provide arbitrary CRAT firmware/platform tables.
3. Reachability analysis
The realistic trigger requires control over malformed CRAT/platform data, typically through firmware, boot environment, ACPI-like platform description, or a hypervisor in virtualized setups. It is not network reachable and not normally reachable by an unprivileged local user. Namespaces and containers do not materially lower the privilege requirement because the input is not a namespaced userspace API. The affected path is device/platform dependent and relevant mainly on systems using AMD KFD/amdkfd CRAT parsing.
4. Severity interpretation
This behaves more like a low-end Moderate or borderline manual-review issue than an Important-class vulnerability. The concrete primitive is an out-of-bounds read, not UAF, OOB write, refcount corruption, arbitrary write, or page-cache/shared-page corruption. Theoretical impact includes driver initialization failure, kernel crash, or limited information exposure, but practical exploitation requires unusually strong control over platform-supplied data.
5. One-sentence report phrase
A malformed CRAT subtype length in amdkfd can cause kfd_parse_subtype() to read beyond the CRAT image boundary, with realistic impact mainly limited to driver failure or kernel DoS under firmware or hypervisor controlled input conditions.
6. Manual review recommendation
MANUAL CHECK RECOMMENDED. This should not be treated as Important by default, but the kernel OOB read in a firmware/platform parser justifies manual confirmation of CRAT controllability and any possible disclosure path.
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: drm/amdkfd: Add bounds check for CRAT subtype length [ Upstream
Commit: ca91e0cc8087568e4b791648a7c01e804f48cb73
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ca91e0cc8087568e4b791648a7c01e804f48cb73
Changed files:
drivers/gpu/drm/amd/amdkfd/kfd_crat.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=ca91e0cc8087568e4b791648a7c01e804f48cb73
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-80747 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80747
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:L
The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H
The Best / paranoid CVSS score: 5.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: 1
Paranoid ActionableScore: 3
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-03 9:30 21% [CVE-2026-80747][MODERATE REGULAR] drm/amdkfd: Add bounds check for CRAT subtype length [ 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