dbcve.org
Linux KernelOperating system · Linux

CVE-2024-35799

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 6.6.26 / 6.7.12 or later.
See remediation →
57/100
Remediation priority · Elevated
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: Prevent crash when disable stream [Why] Disabling stream encoder invokes a function that no longer exists. [How] Check if the function declaration is NULL in disable stream encoder.

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
How this class of weakness works · CWE-400

A single request can consume unbounded CPU, memory, or connections, so a modest amount of malicious traffic exhausts the service. The result is denial of service for everyone else. Remediation is enforcing limits, quotas, and timeouts on what any one request can use.

General guidance for the uncontrolled resource consumption class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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, < 6.6.26>= 6.7, < 6.7.12>= 6.8, < 6.8.3= 6.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 6.6.26 / 6.7.12 / 6.8.3 or later
Fixed in 6.6.266.7.126.8.3
Vendor patch git.kernel.org →
Recommended fix High confidence

Kernel 6.6.26+, 6.7.12+, 6.8.3+, or 6.10+ depending on your branch

  1. Identify your current kernel version using 'uname -r'
  2. Download or install a kernel version that includes the fix: 6.6.26 or later for 6.6.x kernels, 6.7.12 or later for 6.7.x kernels, 6.8.3 or later for 6.8.x kernels, or 6.10 or later for newer kernels
  3. For distribution-specific kernels, apply the vendor patch from commit 2b17133a0a2e0e111803124dad09e803718d4a48 or update to the latest kernel package provided by your distribution
  4. Reboot the system into the fixed kernel version
  5. Verify the running kernel version with 'uname -r' and confirm it is a patched version
Caveat Major kernel upgrades may require rebuilding out-of-tree kernel modules; verify AMD display drivers are compatible with the new kernel version

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,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35799 — 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-35799 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