dbcve.org
Linux KernelOperating system · Linux

CVE-2024-44966

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-04
Fix available
A fix is available. Upgrade to 5.15.165 / 6.1.106 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: binfmt_flat: Fix corruption when not offsetting data start Commit 04d82a6d0881 ("binfmt_flat: allow not offsetting data start") introduced a RISC-V specific variant of the FLAT format which does not allocate any space for the (obsolete) array of shared library pointers. However, it did not disable the code which initializes the array, resulting in the corruption of sizeof(long) bytes before the DATA segment, generally the end of the TEXT segment. Introduce MAX_SHARED_LIBS_UPDATE which depends on the state of CONFIG_BINFMT_FLAT_NO_DATA_START_OFFSET to guard the initialization of the shared library pointer region so that it will only be initialized if space is reserved for it.

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

A 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
Affected:>= 5.13, < 5.15.165>= 5.16, < 6.1.106>= 6.2, < 6.6.47>= 6.7, < 6.10.6= 6.11

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 5.15.165 / 6.1.106 / 6.6.47 or later
Fixed in 5.15.1656.1.1066.6.47
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel version 5.15.165+, 6.1.106+, 6.6.47+, or 6.10.6+ (or the latest stable kernel available for your distribution)

  1. Identify the currently running kernel version using 'uname -r'
  2. Determine which Linux distribution and version is in use (e.g., Ubuntu, Debian, Red Hat, etc.)
  3. For Debian/Ubuntu: Run 'sudo apt-get update && sudo apt-get dist-upgrade' or check for kernel updates via 'apt-cache policy linux-image-generic'
  4. For Red Hat/CentOS: Run 'sudo yum update kernel' or 'sudo dnf update kernel'
  5. For other distributions: Use the distribution's package manager to update to a kernel version >= 5.15.165, >= 6.1.106, >= 6.6.47, or >= 6.10.6 as appropriate for your base version
  6. Reboot the system to load the new kernel: 'sudo reboot'
  7. Verify the fix is applied by running 'uname -r' and confirming the version matches or exceeds the fixed versions
  8. If building from source: Apply the vendor patch from https://git.kernel.org/stable/c/3a684499261d0f7ed5ee72793025c88c2276809c and rebuild the kernel
Caveat Kernel upgrades may require rebuilding out-of-tree modules; ensure third-party kernel modules are compatible with the new 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 $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-44966 — 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-44966 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