dbcve.org
Linux KernelOperating system · Linux

CVE-2024-35997

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-20
Fix available
A fix is available. Upgrade to 4.19.313 / 5.4.275 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: HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up The flag I2C_HID_READ_PENDING is used to serialize I2C operations. However, this is not necessary, because I2C core already has its own locking for that. More importantly, this flag can cause a lock-up: if the flag is set in i2c_hid_xfer() and an interrupt happens, the interrupt handler (i2c_hid_irq) will check this flag and return immediately without doing anything, then the interrupt handler will be invoked again in an infinite loop. Since interrupt handler is an RT task, it takes over the CPU and the flag-clearing task never gets scheduled, thus we have a lock-up. Delete this unnecessary flag.

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-667

Shared resources are accessed without correct locking, so concurrent operations interleave into inconsistent — and sometimes exploitable — states, or deadlock the service outright. These bugs are subtle and timing-dependent. The fix is correct, consistent locking or atomic operations around every shared resource.

General guidance for the improper locking 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:>= 3.8, < 4.19.313>= 4.20, < 5.4.275>= 5.5, < 5.10.216>= 5.11, < 5.15.158>= 5.16, < 6.1.90>= 6.2, < 6.6.30>= 6.7, < 6.8.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 4.19.313 / 5.4.275 / 5.10.216 or later
Fixed in 4.19.3135.4.2755.10.216
Vendor patch git.kernel.org →
Recommended fix High confidence

4.19.313 or 5.4.275 or 5.10.216 or 5.15.158 (depending on which branch you are on)

  1. Identify the currently running Linux kernel version using `uname -r`
  2. Check which of the affected version ranges your kernel falls into (3.8-4.19.312, 4.20-5.4.274, 5.5-5.10.215, or 5.11-5.15.157)
  3. Upgrade the Linux kernel to a version at or above the first fixed version for your branch: 4.19.313, 5.4.275, 5.10.216, or 5.15.158
  4. For distribution-based systems (Ubuntu, Debian, Red Hat, etc.), use the distribution's package manager to install the updated kernel (e.g., `apt update && apt upgrade` or `yum update`)
  5. Reboot the system to load the new kernel
  6. Verify the new kernel version is running with `uname -r` and confirm it includes the fix from commit 0561b65fbd53d3e788c5b0222d9112ca016fd6a1
Caveat Kernel upgrades carry standard upgrade risks; ensure compatibility with custom modules and drivers before deploying in production

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