dbcve.org
Debian LinuxOperating system · Debian

CVE-2024-49996

HIGH · 7.8 CVSS v3.1 Published 2024-10-21
Fix available
A fix is available. Upgrade to 5.4.287 / 5.10.231 or later.
See remediation →
80/100
Remediation priority · High
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: cifs: Fix buffer overflow when parsing NFS reparse points ReparseDataLength is sum of the InodeType size and DataBuffer size. So to get DataBuffer size it is needed to subtract InodeType's size from ReparseDataLength. Function cifs_strndup_from_utf16() is currentlly accessing buf->DataBuffer at position after the end of the buffer because it does not subtract InodeType size from the length. Fix this problem and correctly subtract variable len. Member InodeType is present only when reparse buffer is large enough. Check for ReparseDataLength before accessing InodeType to prevent another invalid memory access. Major and minor rdev values are present also only when reparse buffer is large enough. Check for reparse buffer size before calling reparse_mkdev().

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

A fixed-size buffer is filled without checking the length of the incoming data, so it overflows into neighbouring memory. This is the classic overflow attackers use to overwrite return addresses and hijack execution. The fix is strict length checks and safe, bounded string and memory functions.

General guidance for the classic buffer overflow 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
Debian LinuxOperating system
Affected:= 11.0
Linux KernelOperating system
Affected:>= 5.3, < 5.4.287>= 5.5, < 5.10.231>= 5.11, < 5.15.174>= 5.16, < 6.1.120>= 6.2, < 6.6.55>= 6.7, < 6.10.14>= 6.11, < 6.11.3

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
High
Integrity
High
Availability
High

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

Kernel 5.4.287+, 5.10.231+, 5.15.174+, 6.1.120+, or 6.12+ depending on your distribution's kernel branch

  1. 1. Identify the current kernel version using 'uname -r'
  2. 2. Check if the current version is among the affected versions: 5.3 to <5.4.287, 5.5 to <5.10.231, 5.11 to <5.15.174, or 5.16 to <6.1.120
  3. 3. For Debian 11 (Bullseye), upgrade to kernel 5.4.287 or later (e.g., 5.4.289 or later stable)
  4. 4. For other distributions using kernel 5.10.x, upgrade to 5.10.231 or later
  5. 5. For distributions using kernel 5.15.x, upgrade to 5.15.174 or later
  6. 6. For distributions using kernel 6.1.x, upgrade to 6.1.120 or later
  7. 7. If running a distribution with mainline kernels, upgrade to 6.12 or later which includes the fix
  8. 8. After kernel upgrade, reboot the system to load the fixed kernel
Caveat Kernel upgrades may require updating kernel modules or drivers; ensure compatible firmware and drivers are available for the new kernel version before rebooting

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 $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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