CVE-2026-93125: bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max
Noroxi assessment
Priority: Monitor (action score 31/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.12% (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 00bb52be60da16cd5ead4eb9f8ddc9a66d003ff2, 2147065d3a4e1d5d42ae553fef165f17ec5e0e79, 2aaf67f0516fde29620d0edfc29c01b9ea7ad430; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 00bb52be60da16cd5ead4eb9f8ddc9a66d003ff2, 2147065d3a4e1d5d42ae553fef165f17ec5e0e79, 2aaf67f0516fde29620d0edfc29c01b9ea7ad430; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max check_kfunc_args() detects a kfunc argument named rdonly_buf_size or rdwr_buf_size and stores reg->var_off.value into meta->r0_size, a u64, and does not bound it. check_kfunc_call() later copies that value into the returned register's mem_size field: meta->r0_size = reg->var_off.value; ... regs[BPF_REG_0].mem_size = meta.r0_size; regs[BPF_REG_0].mem_size is u32. A constant whose upper 32 bits are set gets truncated instead of causing a load-time rejection, so the verifier records a PTR_TO_MEM register with an approximately 4 GiB mem_size for whatever allocation the kfunc returned. A later access check against that register uses the truncated, wrong bound. Reject rdonly_buf_size/rdwr_buf_size values that exceed U32_MAX at the point meta->r0_size is set.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Is your version affected? Check itNoroxi 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.
—
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
- 6.1affected
- eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae and later · before 00bb52be60da16cd5ead4eb9f8ddc9a66d003ff2affected · git
- eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae and later · before 2147065d3a4e1d5d42ae553fef165f17ec5e0e79affected · git
- eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae and later · before b6ac0b5732047d43172b9dfbe6b57b9b8de303c2affected · git
- eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae and later · before 93a20b14f8627b2d3486e3ec1d3f2e7275a506ecaffected · git
- eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae and later · before 56a3846830ac95a472297d0cbba75cbff29540bbaffected · git
- eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae and later · before 2aaf67f0516fde29620d0edfc29c01b9ea7ad430affected · git
- before 6.1not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
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.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93123Sep 17, 2026 · serial: qcom-geni: do not advance stale DMA completions0Monitor
- ← EarlierCVE-2026-93124Sep 17, 2026 · platform/x86: asus-wireless: Fail probe when there is no ACPI match0Monitor
- Later →CVE-2026-93126Sep 17, 2026 · remoteproc: qcom_q6v5_adsp: Fix reference leak for device node0Monitor
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 | 00bb52be60da16cd5ead4eb9f8ddc9a66d003ff2 | Vendor (CNA) |
| Linux Linux | 2147065d3a4e1d5d42ae553fef165f17ec5e0e79 | Vendor (CNA) |
| Linux Linux | 2aaf67f0516fde29620d0edfc29c01b9ea7ad430 | Vendor (CNA) |
| Linux Linux | 56a3846830ac95a472297d0cbba75cbff29540bb | Vendor (CNA) |
| Linux Linux | 93a20b14f8627b2d3486e3ec1d3f2e7275a506ec | Vendor (CNA) |
| Linux Linux | b6ac0b5732047d43172b9dfbe6b57b9b8de303c2 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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)Show less
- git.kernel.org/stable/c/2147065d3a4e1d5d42ae553fef165f17ec5e0e79
- git.kernel.org/stable/c/2aaf67f0516fde29620d0edfc29c01b9ea7ad430
- git.kernel.org/stable/c/56a3846830ac95a472297d0cbba75cbff29540bb
- git.kernel.org/stable/c/93a20b14f8627b2d3486e3ec1d3f2e7275a506ec
- git.kernel.org/stable/c/b6ac0b5732047d43172b9dfbe6b57b9b8de303c2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.