Linux KernelOperating system · Linux
CVE-2024-35950
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 · uneditedIn the Linux kernel, the following vulnerability has been resolved: drm/client: Fully protect modes[] with dev->mode_config.mutex The modes[] array contains pointers to modes on the connectors' mode lists, which are protected by dev->mode_config.mutex. Thus we need to extend modes[] the same protection or by the time we use it the elements may already be pointing to freed/reused memory.
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 analysisA 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
< 5.4.275>= 5.5, < 5.10.216>= 5.11, < 5.15.156>= 5.16, < 6.1.87>= 6.2, < 6.6.28>= 6.7, < 6.8.7= 6.9
Debian LinuxOperating system
= 10.0CVSS 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 · scoped5.4.2755.10.2165.15.156
Linux Kernel 5.4.275 / 5.10.216 / 5.15.156 / 6.1.87 (depending on your current branch) or Debian 11/12
- Identify the currently running kernel version using 'uname -r'
- Determine which version branch your kernel belongs to (e.g., 5.10.x, 5.15.x, 6.1.x)
- For systems running kernel < 5.4.275: Plan upgrade to kernel 5.4.275 or later
- For systems running kernel >= 5.5 and < 5.10.216: Plan upgrade to kernel 5.10.216 or later
- For systems running kernel >= 5.11 and < 5.15.156: Plan upgrade to kernel 5.15.156 or later
- For systems running kernel >= 5.16 and < 6.1.87: Plan upgrade to kernel 6.1.87 or later
- For Debian 10.0 (Buster) users: Since Debian 10 is end-of-life, upgrade to Debian 11 (Bullseye) or Debian 12 (Bookworm) to receive kernel security updates
- After upgrade, verify the fix is applied by checking the kernel version matches or exceeds the fixed release for your branch
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35950 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35950 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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