Security readout for executives and security teams
Plain-English summary
A Linux AMD display-driver flaw can let an internal state count exceed an eight-entry clock table, causing an out-of-bounds access. The supplied CVSS rates potential confidentiality and availability impact highly, but exploitation requires local, low-privileged access. The sources do not establish real-world exploitation or describe demonstrated impact.
Executive priority
Treat as a high-priority patching issue for exposed AMD graphics systems, especially multi-user endpoints. It is less urgent than remotely exploitable or confirmed-exploited vulnerabilities because local privileges are required and active exploitation is unsupported. Resolve through the normal accelerated kernel-update cycle after confirming vendor applicability.
Technical view
Within drm/amd/display, fpu_update_bw_bounding_box can process soc.num_states values up to 40 while bw_params->clk_table.entries contains eight elements. The kernel resolution adds an assertion when the state count exceeds eight. Supplied stable-kernel commits document the fix; reachability conditions and practical consequences are not fully described.
Likely exposure
Exposure is limited to Linux systems using affected kernel revisions and the relevant AMD display code path. The bundle marks 4.15, 6.6.50, 6.10.9, and 6.11 as affected, but its version data is incomplete or ambiguous. Confirm exact exposure against distributor advisories and backport status.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. CISA KEV status is false, and no supplied source reports active exploitation or a public proof of concept. Whether an attacker can reliably reach or control the overrun condition is not established.
Researcher notes
The core defect is a possible array overrun caused by a state-count mismatch: up to 40 states versus eight clock-table entries. The stated resolution asserts when the count exceeds eight. Sources do not identify a CWE, proven memory-corruption primitive, triggering hardware configurations, or exploitation reliability, so deeper impact claims would be speculative.
Mitigation direction
- Install a vendor-supported kernel release containing the applicable stable-kernel fix.
- Check distribution security advisories for backported fixes before relying on kernel version numbers.
- Prioritize affected endpoints where untrusted local users or workloads can access graphics functionality.
- Apply normal change controls because kernel updates commonly require rebooting and compatibility validation.
Validation and detection
- Inventory kernel builds and identify systems using AMD display hardware or drivers.
- Compare vendor patch metadata with the three supplied stable-kernel fix commits.
- Verify the running kernel after remediation, including completion of any required reboot.
- Review kernel and graphics-related logs for crashes or warnings; these are indicators, not proof of exploitation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-46811 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H1.85.5LinuxVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/4003bac784380fed1f94f197350567eaa73a409dCVE reference, Linux
- https://git.kernel.org/stable/c/aba188d6f4ebaf52acf13f204db2bd2c22072504CVE reference, Linux
- https://git.kernel.org/stable/c/188fd1616ec43033cedbe343b6579e9921e2d898CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.