Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-41009: bpf: Fix overrunning reservations in ringbuf

MediumCVSS 5.5 · v3.1—No exploit Fix available

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.27% (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 0f98f40eb1ed52af8b81f61901b6c0289ff59de4, 47416c852f2a04d348ea66ee451cbdcf8119f225, 511804ab701c0503b72eac08217eabfd366ba069; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.43.1-7; azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 6.6.43.1-7.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0f98f40eb1ed52af8b81f61901b6c0289ff59de4, 47416c852f2a04d348ea66ee451cbdcf8119f225, 511804ab701c0503b72eac08217eabfd366ba069; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.43.1-7; azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 6.6.43.1-7 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: Fix overrunning reservations in ringbuf The BPF ring buffer internally is implemented as a power-of-2 sized circular buffer, with two logical and ever-increasing counters: consumer_pos is the consumer counter to show which logical position the consumer consumed the data, and producer_pos which is the producer counter denoting the amount of data reserved by all producers. Each time a record is reserved, the producer that "owns" the record will successfully advance producer counter. In user space each time a record is read, the consumer of the data advanced the consumer counter once it finished processing. Both counters are stored in separate pages so that from user space, the producer counter is read-only and the consumer counter is read-write. One aspect that simplifies and thus speeds up the implementation of both producers and consumers is how the data area is mapped twice contiguously back-to-back in the virtual memory, allowing to not take any special measures for samples that have to wrap around at the end of the circular buffer data area, because the next page after the last data page would be first data page again, and thus the sample will still appear completely contiguous in virtual memory. Each record has a struct bpf_ringbuf_hdr { u32 len; u32 pg_off; } header for book-keeping the length and offset, and is inaccessible to the BPF program. Helpers like bpf_ringbuf_reserve() return `(void *)hdr + BPF_RINGBUF_HDR_SZ` for the BPF program to use. Bing-Jhong and Muhammad reported that it is however possible to make a second allocated memory chunk overlapping with the first chunk and as a result, the BPF program is now able to edit first chunk's header. For example, consider the creation of a BPF_MAP_TYPE_RINGBUF map with size of 0x4000. Next, the consumer_pos is modified to 0x3000 /before/ a call to bpf_ringbuf_reserve() is made. This will allocate a chunk A, which is in [0x0,0x3008], and the BPF program is able to edit [0x8,0x3008]. Now, lets allocate a chunk B with size 0x3000. This will succeed because consumer_pos was edited ahead of time to pass the `new_prod_pos - cons_pos > rb->mask` check. Chunk B will be in range [0x3008,0x6010], and the BPF program is able to edit [0x3010,0x6010]. Due to the ring buffer memory layout mentioned earlier, the ranges [0x0,0x4000] and [0x4000,0x8000] point to the same data pages. This means that chunk B at [0x4000,0x4008] is chunk A's header. bpf_ringbuf_submit() / bpf_ringbuf_discard() use the header's pg_off to then locate the bpf_ringbuf itself via bpf_ringbuf_restore_from_rec(). Once chunk B modified chunk A's header, then bpf_ringbuf_commit() refers to the wrong page and could cause a crash. Fix it by calculating the oldest pending_pos and check whether the range from the oldest outstanding record to the newest would span beyond the ring buffer size. If that is the case, then reject the request. We've tested with the ring buffer benchmark in BPF selftests (./benchs/run_bench_ringbufs.sh) before/after the fix and while it seems a bit slower on some benchmarks, it is still not significantly enough to matter.

Published
Jul 17, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 19th 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.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

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.8affected
    • 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before be35504b959f2749bab280f4671e8df96dcf836faffected · git
    • 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before 0f98f40eb1ed52af8b81f61901b6c0289ff59de4affected · git
    • 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before d1b9df0435bc61e0b44f578846516df8ef476686affected · git
    • 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before 511804ab701c0503b72eac08217eabfd366ba069affected · git
    • 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before 47416c852f2a04d348ea66ee451cbdcf8119f225affected · git
    • 457f44363a8894135c85b7a9afd2bd8196db24ab and later · before cfa1a2329a691ffd991fcf7248a57d752e712881affected · git
    • before 5.8not affected · semver
    • 5.10.223 and later · up to and including 5.10.*not affected · semver
    • 5.15.164 and later · up to and including 5.15.*not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.8 and later · before 6.1.97
  • linux linux kernel6.2 and later · before 6.6.37
  • linux linux kernel6.7 and later · before 6.9.8

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.4.0-503.15.1.el9_57.4.0-503.15.1.el9_5
AlmaLinux:9kernelbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64kbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-corebefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-debugbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-develbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-corebefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-cross-headersbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-debugbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-debug-corebefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-debug-develbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-503.15.1.el9_55.14.0-503.15.1.el9_5

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2022-48828Jul 16, 2024 · NFSD: Fix ia_size underflow
    22Monitor
  • ← EarlierCVE-2022-48829Jul 16, 2024 · NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes
    22Monitor
  • Later →CVE-2024-41010Jul 17, 2024 · bpf: Fix too early release of tcx_entry
    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 Linux0f98f40eb1ed52af8b81f61901b6c0289ff59de4Vendor (CNA)
Linux Linux47416c852f2a04d348ea66ee451cbdcf8119f225Vendor (CNA)
Linux Linux511804ab701c0503b72eac08217eabfd366ba069Vendor (CNA)
Linux Linuxbe35504b959f2749bab280f4671e8df96dcf836fVendor (CNA)
Linux Linuxcfa1a2329a691ffd991fcf7248a57d752e712881Vendor (CNA)
Linux Linuxd1b9df0435bc61e0b44f578846516df8ef476686Vendor (CNA)
azl3 kernel 6.6.35.1-5 on Azure Linux 3.06.6.43.1-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.43.1-7 on Azure Linux 3.06.6.43.1-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.164.1-1 on CBL Mariner 2.05.15.164.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.05.15.164.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.05.15.164.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool7.4.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-503.15.1.el9_5 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.98-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.81.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)

+6

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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2021-47137114 days apartnet: lantiq: fix memory corruption in RX ring
    39Monitor
  • CVE-2024-3596958 days apartipv6: fix race condition between ipv6_get_ifaddr and ipv6_del_addr
    35Monitor
  • CVE-2024-3402723 days apartf2fs: compress: fix to cover {reserve,release}_compress_blocks() w/ cp_rwsem lock
    31Monitor
  • CVE-2021-4755154 days apartdrm/amd/amdkfd: Fix kernel panic when reset failed and been triggered again
    31Monitor
  • CVE-2021-47130124 days apartnvmet: fix freeing unallocated p2pmem
    30Monitor
  • CVE-2024-2689491 days apartACPI: processor_idle: Fix memory leak in acpi_processor_power_exit()
    24Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

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

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

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

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

References

All records