Look up another CVE · open CVE-2024-46811 in the interactive tracker
CVE-2024-46811
drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box
Published 2024-09-27 (2 years ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2024-46811 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.10.9-1 | Update the kernel and reboot. Fixed in 6.10.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.10.9-1 | Update the kernel and reboot. Fixed in 6.10.9-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.10.9-1 | Update the kernel and reboot. Fixed in 6.10.9-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
[Why] Coverity reports OVERRUN warning. soc.num_states could be 40. But array range of bw_params->clk_table.entries is 8. [How] Assert if soc.num_states greater than 8.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/gpu/drm/amd/display/dc/dml/dcn302/dcn302_fpu.c
drivers/gpu/drm/amd/display/dc/dml/dcn303/dcn303_fpu.c
drivers/gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c
drivers/gpu/drm/amd/display/dc/dml/dcn321/dcn321_fpu.c
- What this is
- AMD DISPLAY CORE - DMLMAINTAINERS section matched on drivers/gpu/drm/amd/display/dc/dml/ · Supported
Show whether Debian builds this, per release
Not established. This site could not find the build rule for the affected file in the kernel trees Debian ships, so it has no answer about whether Debian compiles this code. Read that as unknown, never as absent.
- bookworm, trixie, forky, sid?
- ?
- not established - no Makefile entry for the affected file
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS
Signals
- Published
- 2024-09-27 (2 years ago)source
- CVSS
- 7.3 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.25%, higher than 14.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/gpu
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.15 | 6.6.50 | 4003bac78438 |
| 4.15 | 6.10.9 | aba188d6f4eb |
| 4.15 | 6.11 | 188fd1616ec4 |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The vulnerable code is reached only through amdgpu DC initialization paths on the local machine — `dc_construct()`, `dcn32_init_hw()`, and `get_memclk_states_from_smu()` during hardware init and suspend/resume. There is no network, adjacent-network, or physical-device vector.
- AC:LAttack complexity, low
- On affected hardware the overrun happens deterministically whenever the firmware-reported DPM level count plus the hardcoded DCFCLK STA targets exceeds 8 — no race to win, no memory layout to groom, and no unlikely precondition. The vulnerable path in dcn302/dcn303 is entirely ungated.
- PR:LPrivileges required, low
- The trigger points (DC hardware init and resume of the DRM device) are reachable in an ordinary unprivileged desktop session via logind-mediated suspend/resume of the GPU, without root in the init namespace. No pre-authentication or remote path exists, so PR:N is not supportable.
- UI:NUser interaction, none
- The bounding-box update runs automatically during driver hardware init and resume; no victim action such as opening a file or plugging in a display is required.
- S:UScope, unchanged
- The out-of-bounds read and the resulting corrupted DML bounding box are both entirely within the kernel's own security authority — there is no VM, IOMMU, or sandbox boundary crossed.
- C:HConfidentiality impact, high
- With `num_states` able to reach `DC__VOLTAGE_STATES` (40) against an 8-element `entries[]`, the read runs up to ~1.3 KB past the end of the `struct clk_bw_params` allocation into adjacent slab memory — far beyond a "few bytes" bounded read. Those bytes are copied into `dml.soc.clock_limits[]`, which feeds userspace-observable clock and mode-validation state.
- I:LIntegrity impact, low
- There is no out-of-bounds write — `clock_limits[]` is 40 entries and the index is bounded by that — but attacker-uncontrolled garbage from adjacent memory is written into the DML soc bounding box and then used to program dispclk/dppclk/dcfclk/socclk, corrupting kernel state that drives real display hardware.
- A:HAvailability impact, high
- Reading past the end of the heap-allocated `clk_bw_params` can fault or oops and reliably trips KASAN, and feeding nonsensical clock/voltage limits into DML can hang or blank the display pipeline. Any such kernel crash or hang is High.