Linux KernelOperating system · Linux
CVE-2024-47728
A fix is available.
Upgrade to 6.1.113 / 6.6.54 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 · uneditedIn the Linux kernel, the following vulnerability has been resolved: bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error For all non-tracing helpers which formerly had ARG_PTR_TO_{LONG,INT} as input arguments, zero the value for the case of an error as otherwise it could leak memory. For tracing, it is not needed given CAP_PERFMON can already read all kernel memory anyway hence bpf_get_func_arg() and bpf_get_func_ret() is skipped in here. Also, the MTU helpers mtu_len pointer value is being written but also read. Technically, the MEM_UNINIT should not be there in order to always force init. Removing MEM_UNINIT needs more verifier rework though: MEM_UNINIT right now implies two things actually: i) write into memory, ii) memory does not have to be initialized. If we lift MEM_UNINIT, it then becomes: i) read into memory, ii) memory must be initialized. This means that for bpf_*_check_mtu() we're readding the issue we're trying to fix, that is, it would then be able to write back into things like .rodata BPF maps. Follow-up work will rework the MEM_UNINIT semantics such that the intent can be better expressed. For now just clear the *mtu_len on error path which can be lifted later again.
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 analysisA 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.2, < 6.1.113>= 6.2, < 6.6.54>= 6.7, < 6.10.13>= 6.11, < 6.11.2CVSS 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 6.1.113 / 6.6.54 / 6.10.13 or later
Fixed in
6.1.1136.6.546.10.13
Vendor patch
git.kernel.org →
Recommended fix
High confidence
Linux Kernel 6.1.113, 6.6.54, 6.10.13, or 6.11.2 (or later stable)
- 1. Identify the currently running Linux kernel version using 'uname -r'
- 2. Check if the current version is one of the affected versions: 5.2 to <6.1.113, 6.2 to <6.6.54, 6.7 to <6.10.13, or 6.11 to <6.11.2
- 3. Plan a kernel upgrade to a patched stable release: upgrade to kernel 6.1.113 or later, 6.6.54 or later, 6.10.13 or later, or 6.11.2 or later
- 4. Backup current kernel configuration and important data before upgrading
- 5. Obtain the patched kernel from your Linux distribution's official repositories or kernel.org
- 6. Install the new kernel package following distribution-specific procedures (e.g., 'apt-get install linux-image-<version>' for Debian/Ubuntu, 'yum install kernel-<version>' for RHEL/CentOS, or compile from source)
- 7. Reboot the system into the new kernel
- 8. Verify the new kernel version is running with 'uname -r' and confirm it matches a fixed release
Caveat Kernel upgrades may introduce compatibility issues with custom modules or specific hardware drivers; ensure all proprietary drivers are compatible with the target kernel version before production deployment
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-47728 — 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-47728 in production — separate from our analysis above.
Know something about CVE-2024-47728?
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.
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