LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38080: drm/amd/display: Increase block_sequence array size

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Increase block_sequence array size [Why] It's possible to generate more than 50 steps in hwss_build_fast_sequence, for example with a 6-pipe asic where all pipes are in one MPC chain. This overflows the block_sequence buffer and corrupts block_sequence_steps, causing a crash. [How] Expand block_sequence to 100 items. A naive upper bound on the possible number of steps for a 6-pipe asic, ignoring the potential for steps to be mutually exclusive, is 91 with current code, therefore 100 is sufficient.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux AMD display driver can overflow an internal sequence buffer during complex display-pipeline processing, corrupt nearby state and causing a system crash. The supplied CVSS score is 7.8 because a local, low-privileged user may trigger memory corruption without user interaction. Systems without the affected AMD display path are unlikely to be exposed.

Executive priority

Treat as a high-priority workstation and multi-user Linux update, especially where affected AMD graphics are present. It is not supported as an internet-remote threat by these sources. Patch through normal emergency maintenance based on vendor applicability, while prioritizing systems where untrusted users can obtain local access.

Technical view

The fixed-size block_sequence array held 50 entries, but hwss_build_fast_sequence can generate more, including up to 91 under a stated six-pipe configuration with one MPC chain. Overflow corrupts block_sequence_steps and causes a crash. Linux resolved this by expanding the array to 100 entries across applicable stable branches.

Likely exposure

Exposure is limited to affected Linux kernels using the AMD display driver and a display configuration capable of producing an oversized hardware sequence. Local access with low privileges is required according to the CVSS vector. The supplied version data is ambiguous, so distribution package status and incorporated stable commits should determine exposure.

Exploitation context

The supplied record does not identify CISA KEV listing or active exploitation. It describes a locally reachable, low-complexity condition requiring low privileges and no user interaction. Although the CVSS vector rates confidentiality, integrity, and availability impacts high, the cited technical description specifically demonstrates buffer corruption and a crash; broader impact is not established here.

Researcher notes

The source establishes an array-bound error in AMD display sequence construction and a corrective capacity increase from 50 to 100. A stated naive upper bound is 91 for current six-pipe logic. No CWE is supplied. Exact vulnerable version ranges, reachability across ASIC families, reliable triggering conditions, and impact beyond corruption-induced crashing remain insufficiently documented in the bundle.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix.
  • Check distribution security guidance because the supplied affected-version boundaries are ambiguous.
  • Prioritize multi-user workstations and systems exposing affected AMD display hardware.
  • Restrict unnecessary local accounts until updates are applied.

Validation and detection

  • Inventory Linux kernel versions and systems using the AMD display driver.
  • Compare kernel package changelogs against the four cited stable commits.
  • Confirm the installed source or vendor build expands block_sequence to 100 entries.
  • Review kernel crash records for AMD display sequence failures or related memory corruption.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38080 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-38080Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c, 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7cunaffected
LinuxLinux4.15, 0, 6.6.93, 6.12.31, 6.14.9, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.