Linux KernelOperating system · Linux
CVE-2024-57910
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: iio: light: vcnl4035: fix information leak in triggered buffer The 'buffer' local array is used to push data to userspace from a triggered buffer, but it does not set an initial value for the single data element, which is an u16 aligned to 8 bytes. That leaves at least 4 bytes uninitialized even after writing an integer value with regmap_read(). Initialize the array to zero before using it to avoid pushing uninitialized information to userspace.
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 analysisMemory or a resource is used before it has been initialised, so its contents are whatever happened to be there — sometimes leaking earlier data, sometimes values an attacker can influence. Behaviour becomes unpredictable and occasionally exploitable. Remediation is initialising every resource before use and ensuring initialisation happens on all code paths.
General guidance for the use of uninitialized resource 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
>= 5.4.132, < 5.4.290>= 5.10.50, < 5.10.234>= 5.12.17, < 5.13>= 5.13.2, < 5.15.177>= 5.16, < 6.1.125>= 6.2, < 6.6.72>= 6.7, < 6.12.10= 6.13CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.2905.10.2345.13
Upgrade to Linux kernel 5.4.290+, 5.10.234+, 5.13+, or 5.15.177+ depending on which branch you are currently running
- Identify the current running kernel version using 'uname -r'
- Check which of the affected version ranges your kernel falls into (5.4.132-5.4.289, 5.10.50-5.10.233, 5.12.17-5.12.x, or 5.13.2-5.15.176)
- Upgrade the Linux kernel to a version that includes the fix: for 5.4.x kernels upgrade to >= 5.4.290, for 5.10.x upgrade to >= 5.10.234, for 5.12.x upgrade to 5.13 or later, for 5.13.x-5.15.x upgrade to >= 5.15.177
- After kernel upgrade, reboot the system to load the fixed kernel
- Verify the fix is applied by checking the vcnl4035 driver source code for zero-initialization of the buffer array, or confirm via kernel release notes that CVE-2024-57910 is resolved
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-57910 — 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-57910 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