dbcve.org
Linux KernelOperating system · Linux

CVE-2024-42119

HIGH · 7.8 CVSS v3.1 Published 2024-07-30
Fix available
A fix is available. Upgrade to 4.19.318 / 5.4.280 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: Skip finding free audio for unknown engine_id [WHY] ENGINE_ID_UNKNOWN = -1 and can not be used as an array index. Plus, it also means it is uninitialized and does not need free audio. [HOW] Skip and return NULL. This fixes 2 OVERRUN issues reported by Coverity.

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
Linux KernelOperating system
Affected:>= 4.15, < 4.19.318>= 4.20, < 5.4.280>= 5.5, < 5.10.222>= 5.11, < 5.15.163>= 5.16, < 6.1.98>= 6.2, < 6.6.39>= 6.7, < 6.9.9

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 4.19.318 / 5.4.280 / 5.10.222 or later
Fixed in 4.19.3185.4.2805.10.222
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel version 4.19.318 or later (for 4.19.x branches), 5.4.280 or later (for 5.4.x branches), 5.10.222 or later (for 5.10.x branches), or 5.15.163 or later (for 5.15.x branches). For production systems, consider the latest stable 5.15.x or 6.x kernel for broader security updates.

  1. Identify your current kernel version using `uname -r`
  2. Check which distribution branch your kernel belongs to (4.19.x, 5.4.x, 5.10.x, or 5.15.x)
  3. Update your system packages to get the latest kernel security updates. For Debian/Ubuntu: `sudo apt update && sudo apt upgrade`
  4. For RHEL/CentOS: `sudo yum update`
  5. For Fedora: `sudo dnf update`
  6. Reboot the system to load the new kernel: `sudo reboot`
  7. Verify the new kernel version is running: `uname -r`
  8. Confirm the version includes the fix (4.19.318+, 5.4.280+, 5.10.222+, or 5.15.163+)
Caveat Kernel upgrades may require rebuild of third-party kernel modules (like NVIDIA drivers) and a system reboot. Some driver compatibility may vary across kernel minor versions.

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-42119 — 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-42119 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