Skip to content
Noroxi
CVE-2024-47728· NVD / CVE Program· CNA Linux

bpf: Zero former ARG_PTR_TO_{LONG,INT} args in case of error

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.23% (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 4b3786a6c5397dc220b1483d8e2f4867743e966f, 594a9f5a8d2de2573a856e506f77ba7dd2cefc6a, 599d15b6d03356a97bff7a76155c5604c42a2962; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 4b3786a6c5397dc220b1483d8e2f4867743e966f, 594a9f5a8d2de2573a856e506f77ba7dd2cefc6a, 599d15b6d03356a97bff7a76155c5604c42a2962; Azure Linux 3.0 ARM 6.6.56.1-5; Azure Linux 3.0 x64 6.6.56.1-5 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: 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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 13th 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.2%

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

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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 kernel5.2 and later · before 6.1.113
  • linux linux kernel6.2 and later · before 6.6.54
  • linux linux kernel6.7 and later · before 6.10.13
  • linux linux kernel6.11 and later · before 6.11.2

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

    • 5.2affected
    • d7a4cb9b6705a89937d12c8158a35a3145dc967a and later · before 8397bf78988f3ae9dbebb0200189a62a57264980affected · git
    • d7a4cb9b6705a89937d12c8158a35a3145dc967a and later · before a634fa8e480ac2423f86311a602f6295df2c8ed0affected · git
    • d7a4cb9b6705a89937d12c8158a35a3145dc967a and later · before 599d15b6d03356a97bff7a76155c5604c42a2962affected · git
    • d7a4cb9b6705a89937d12c8158a35a3145dc967a and later · before 594a9f5a8d2de2573a856e506f77ba7dd2cefc6aaffected · git
    • d7a4cb9b6705a89937d12c8158a35a3145dc967a and later · before 4b3786a6c5397dc220b1483d8e2f4867743e966faffected · git
    • before 5.2not affected · semver
    • 6.1.113 and later · up to and including 6.1.*not affected · semver
    • 6.6.54 and later · up to and including 6.6.*not affected · semver
    • 6.10.13 and later · up to and including 6.10.*not 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.115-16.1.115-1
Debian:13linuxbefore 6.11.2-16.11.2-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-47726Oct 21, 2024 · f2fs: fix to wait dio completion
    26Monitor
  • ← EarlierCVE-2024-47727Oct 21, 2024 · x86/tdx: Fix "in-kernel MMIO" check
    31Monitor
  • Later →CVE-2024-47729Oct 21, 2024 · drm/xe: Use reserved copy engine for user binds on faulting devices
    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 Linux4b3786a6c5397dc220b1483d8e2f4867743e966fVendor (CNA)
Linux Linux594a9f5a8d2de2573a856e506f77ba7dd2cefc6aVendor (CNA)
Linux Linux599d15b6d03356a97bff7a76155c5604c42a2962Vendor (CNA)
Linux Linux8397bf78988f3ae9dbebb0200189a62a57264980Vendor (CNA)
Linux Linuxa634fa8e480ac2423f86311a602f6295df2c8ed0Vendor (CNA)
Azure Linux 3.0 ARM6.6.56.1-5 · kernelMicrosoft (MSRC)
Azure Linux 3.0 x646.6.56.1-5 · kernelMicrosoft (MSRC)
debian:linux6.1.115-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.

Credits

All researchers

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.

  • CVE-2025-37908211 days apartmm, slab: clean up slab->obj_exts always
    31Monitor
  • CVE-2021-47110220 days apartx86/kvm: Disable kvmclock on all CPUs on shutdown
    28Monitor
  • CVE-2024-476930 days apartIB/core: Fix ib_cache_setup_one error flow cleanup
    26Monitor
  • CVE-2022-490120 days apartafs: Fix server->active leak in afs_put_server
    22Monitor
  • CVE-2022-490280 days apartixgbevf: Fix resource leak in ixgbevf_init_module()
    22Monitor
  • CVE-2024-477310 days apartdrivers/perf: Fix ali_drw_pmu driver interrupt status clearing
    22Monitor

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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-459 · Incomplete Cleanup

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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

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

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records