dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-49894

HIGH · 7.8 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to 3.2 / 4.19.323 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix index out of bounds in degamma hardware format translation Fixes index out of bounds issue in `cm_helper_translate_curve_to_degamma_hw_format` function. The issue could occur when the index 'i' exceeds the number of transfer function points (TRANSFER_FUNC_POINTS). The fix adds a check to ensure 'i' is within bounds before accessing the transfer function points. If 'i' is out of bounds the function returns false to indicate an error. Reported by smatch: drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:594 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.red' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:595 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.green' 1025 <= s32max drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_cm_common.c:596 cm_helper_translate_curve_to_degamma_hw_format() error: buffer overflow 'output_tf->tf_pts.blue' 1025 <= s32max

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 11.0
Linux KernelOperating system
Affected:>= 4.15, < 4.19.323>= 4.20, < 5.4.285>= 5.5, < 5.10.227>= 5.11, < 5.15.168>= 5.16, < 6.1.113>= 6.2, < 6.6.55>= 6.7, < 6.10.14>= 6.11, < 6.11.3
Simatic S7 1500 Tm Mfp FirmwareOperating system
Affected:= 1.1
Sinec OsOperating system
Affected:< 3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2 / 4.19.323 / 5.4.285 or later
Fixed in 3.24.19.3235.4.285
Vendor patch git.kernel.org →
Recommended fix High confidence

Linux kernel 4.19.323+, 5.4.285+, 5.10.227+, or 5.15.168+ (depending on which branch is in use)

  1. 1. Identify the currently running Linux kernel version using `uname -r`
  2. 2. Determine which kernel branch your version falls into based on the affected ranges: 4.15-4.19.x, 4.20-5.4.x, 5.5-5.10.x, or 5.11-5.15.x
  3. 3. For Debian 11 (Bullseye), check available kernel updates via `apt-cache policy linux-image-*`
  4. 4. Upgrade to a patched kernel version: 4.19.323 or later for 4.19.x, 5.4.285 or later for 5.4.x, 5.10.227 or later for 5.10.x, or 5.15.168 or later for 5.15.x
  5. 5. On Debian, run `sudo apt-get update && sudo apt-get install linux-image-<version>` to install the fixed kernel
  6. 6. Reboot the system to load the patched kernel
  7. 7. Verify the fix is applied by checking the kernel version matches a fixed release and confirming the dcn10_cm_common.c file contains the bounds check
Caveat Kernel upgrades may require rebooting services; ensure compatibility with any custom kernel modules or driver dependencies before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49894 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-49894 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data