Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35997: HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0561b65fbd53d3e788c5b0222d9112ca016fd6a1, 21bfca822cfc1e71796124e93b46e0d9fa584401, 29e94f295bad5be59cf4271a93e22cdcf5536722; azl3 kernel 6.6.29.1-5 on Azure Linux 3.0 6.6.35.1-4; azl3 kernel 6.6.35.1-4 on Azure Linux 3.0 6.6.35.1-4.

Low priority for now. Upgrade to Linux Linux 0561b65fbd53d3e788c5b0222d9112ca016fd6a1, 21bfca822cfc1e71796124e93b46e0d9fa584401, 29e94f295bad5be59cf4271a93e22cdcf5536722; azl3 kernel 6.6.29.1-5 on Azure Linux 3.0 6.6.35.1-4; azl3 kernel 6.6.35.1-4 on Azure Linux 3.0 6.6.35.1-4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 20, 2024
Updated
Oct 15, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-35997

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.8 and later · before 4.19.313
  • linux linux kernel4.20 and later · before 5.4.275
  • linux linux kernel5.5 and later · before 5.10.216
  • linux linux kernel5.11 and later · before 5.15.158
  • linux linux kernel5.16 and later · before 6.1.90
  • linux linux kernel6.2 and later · before 6.6.30
  • linux linux kernel6.7 and later · before 6.8.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.8affected
    • 4a200c3b9a40242652b5734630bdd0bcf3aca75f and later · before 21bfca822cfc1e71796124e93b46e0d9fa584401affected · git
    • 4a200c3b9a40242652b5734630bdd0bcf3aca75f and later · before c448a9fd50f77e8fb9156ff64848aa4295eb3003affected · git
    • 4a200c3b9a40242652b5734630bdd0bcf3aca75f and later · before 5095b93021b899f54c9355bebf36d78854c33a22affected · git
    • 4a200c3b9a40242652b5734630bdd0bcf3aca75f and later · before b65fb50e04a95eec34a9d1bc138454a98a5578d8affected · git
    • 4a200c3b9a40242652b5734630bdd0bcf3aca75f and later · before 0561b65fbd53d3e788c5b0222d9112ca016fd6a1affected · git
    • 4a200c3b9a40242652b5734630bdd0bcf3aca75f and later · before 29e94f295bad5be59cf4271a93e22cdcf5536722affected · git
    • 4a200c3b9a40242652b5734630bdd0bcf3aca75f and later · before 418c5575d56410c6e186ab727bf32ae32447d497affected · git
    • 4a200c3b9a40242652b5734630bdd0bcf3aca75f and later · before 9c0f59e47a90c54d0153f8ddc0f80d7a36207d0eaffected · git
    • before 3.8not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.90-16.1.90-1
Debian:13linuxbefore 6.8.9-16.8.9-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35990May 20, 2024 · dma: xilinx_dpdma: Fix locking
    22Monitor
  • ← EarlierCVE-2024-35996May 20, 2024 · cpu: Re-enable CPU mitigations by default for !X86 architectures
    22Monitor
  • Later →CVE-2024-36004May 20, 2024 · i40e: Do not use WQ_MEM_RECLAIM flag for workqueue
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0561b65fbd53d3e788c5b0222d9112ca016fd6a1Vendor (CNA)
Linux Linux21bfca822cfc1e71796124e93b46e0d9fa584401Vendor (CNA)
Linux Linux29e94f295bad5be59cf4271a93e22cdcf5536722Vendor (CNA)
Linux Linux418c5575d56410c6e186ab727bf32ae32447d497Vendor (CNA)
Linux Linux5095b93021b899f54c9355bebf36d78854c33a22Vendor (CNA)
Linux Linux9c0f59e47a90c54d0153f8ddc0f80d7a36207d0eVendor (CNA)
Linux Linuxb65fb50e04a95eec34a9d1bc138454a98a5578d8Vendor (CNA)
Linux Linuxc448a9fd50f77e8fb9156ff64848aa4295eb3003Vendor (CNA)
azl3 kernel 6.6.29.1-5 on Azure Linux 3.06.6.35.1-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.35.1-4 on Azure Linux 3.06.6.35.1-4 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.153.1-2 on CBL Mariner 2.05.15.158.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.158.1-1 on CBL Mariner 2.05.15.158.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.90-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records