CVE-2024-58100: bpf: check changes_pkt_data property for extension programs
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.19% (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 3846e2bea565ee1c5195dcc625fda9868fb0e3b3, 7197fc4acdf238ec8ad06de5a8235df0c1f9c7d7, 81f6d0530ba031b5f038a091619bf2ff29568852; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 3846e2bea565ee1c5195dcc625fda9868fb0e3b3, 7197fc4acdf238ec8ad06de5a8235df0c1f9c7d7, 81f6d0530ba031b5f038a091619bf2ff29568852; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 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: check changes_pkt_data property for extension programs When processing calls to global sub-programs, verifier decides whether to invalidate all packet pointers in current state depending on the changes_pkt_data property of the global sub-program. Because of this, an extension program replacing a global sub-program must be compatible with changes_pkt_data property of the sub-program being replaced. This commit: - adds changes_pkt_data flag to struct bpf_prog_aux: - this flag is set in check_cfg() for main sub-program; - in jit_subprogs() for other sub-programs; - modifies bpf_check_attach_btf_id() to check changes_pkt_data flag; - moves call to check_attach_btf_id() after the call to check_cfg(), because it needs changes_pkt_data flag to be set: bpf_check: ... ... - check_attach_btf_id resolve_pseudo_ldimm64 resolve_pseudo_ldimm64 --> bpf_prog_is_offloaded bpf_prog_is_offloaded check_cfg check_cfg + check_attach_btf_id ... ... The following fields are set by check_attach_btf_id(): - env->ops - prog->aux->attach_btf_trace - prog->aux->attach_func_name - prog->aux->attach_func_proto - prog->aux->dst_trampoline - prog->aux->mod - prog->aux->saved_dst_attach_type - prog->aux->saved_dst_prog_type - prog->expected_attach_type Neither of these fields are used by resolve_pseudo_ldimm64() or bpf_prog_offload_verifier_prep() (for netronome and netdevsim drivers), so the reordering is safe.
- Published
- May 5, 2025
- Updated
- Oct 15, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_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.6 and later · before 6.6.90
- linux linux kernel6.7 and later · before 6.12.25
- linux linux kernel6.13
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.6affected
- be8704ff07d2374bcc5c675526f95e70c6459683 and later · before 7197fc4acdf238ec8ad06de5a8235df0c1f9c7d7affected · git
- be8704ff07d2374bcc5c675526f95e70c6459683 and later · before 3846e2bea565ee1c5195dcc625fda9868fb0e3b3affected · git
- be8704ff07d2374bcc5c675526f95e70c6459683 and later · before 81f6d0530ba031b5f038a091619bf2ff29568852affected · git
- before 5.6not affected · semver
- 6.6.90 and later · up to and including 6.6.*not affected · semver
- 6.12.25 and later · up to and including 6.12.*not affected · semver
- 6.13 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.25-1 | 6.12.25-1 |
| openSUSE:Leap 15.6 | dtb-aarch64 | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-64kb | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-azure | before 6.4.0-150600.8.40.1 | 6.4.0-150600.8.40.1 |
| openSUSE:Leap 15.6 | kernel-debug | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-default | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-default-base | before 6.4.0-150600.23.53.1.150600.12.24.1 | 6.4.0-150600.23.53.1.150600.12.24.1 |
| openSUSE:Leap 15.6 | kernel-docs | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-kvmsmall | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-obs-build | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-obs-qa | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-source | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-source-azure | before 6.4.0-150600.8.40.1 | 6.4.0-150600.8.40.1 |
| openSUSE:Leap 15.6 | kernel-syms | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| openSUSE:Leap 15.6 | kernel-syms-azure | before 6.4.0-150600.8.40.1 | 6.4.0-150600.8.40.1 |
| openSUSE:Leap 15.6 | kernel-zfcpdump | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6_Update_12 | before 1-150600.13.3.1 | 1-150600.13.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-64kb | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-default | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-default-base | before 6.4.0-150600.23.53.1.150600.12.24.1 | 6.4.0-150600.23.53.1.150600.12.24.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-source | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP6 | kernel-zfcpdump | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP6 | kernel-docs | before 6.4.0-150600.23.53.1 | 6.4.0-150600.23.53.1 |
+11
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-37799May 3, 2025 · vmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp22Monitor
- ← EarlierCVE-2024-58098May 5, 2025 · bpf: track changes_pkt_data property for global functions22Monitor
- Later →CVE-2024-58237May 5, 2025 · bpf: consider that tail calls invalidate packet pointers22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3846e2bea565ee1c5195dcc625fda9868fb0e3b3 | Vendor (CNA) |
| Linux Linux | 7197fc4acdf238ec8ad06de5a8235df0c1f9c7d7 | Vendor (CNA) |
| Linux Linux | 81f6d0530ba031b5f038a091619bf2ff29568852 | Vendor (CNA) |
| azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.92.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.25-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.4.0-150600.23.53.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.4.0-150600.23.53.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-azure | 6.4.0-150600.8.40.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-debug | 6.4.0-150600.23.53.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default | 6.4.0-150600.23.53.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.4.0-150600.23.53.1.150600.12.24.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-docs | 6.4.0-150600.23.53.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.4.0-150600.23.53.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.4.0-150600.23.53.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.4.0-150600.23.53.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-azure | 6.4.0-150600.8.40.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 6.4.0-150600.8.40.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150600.23.53.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-azure | 6.4.0-150600.8.40.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-default | 6.4.0-150600.23.53.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-default-base | 6.4.0-150600.23.53.1.150600.12.24.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-docs | 6.4.0-150600.23.53.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6_Update_12 | 1-150600.13.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-obs-build | 6.4.0-150600.23.53.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:kernel-source | 6.4.0-150600.23.53.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
| suse:kernel-source-azure | 6.4.0-150600.8.40.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-syms | 6.4.0-150600.23.53.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:kernel-syms-azure | 6.4.0-150600.8.40.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
+1
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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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.
No nightly-computed relations.
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).
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)
—
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.