CVE-2026-45886bpf: Fix bpf_xdp_store_bytes proto for read-only arg
- 5.5MediumCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix bpf_xdp_store_bytes proto for read-only arg While making some maps in Cilium read-only from the BPF side, we noticed that the bpf_xdp_store_bytes proto is incorrect. In particular, the verifier was throwing the following error: ; ret = ctx_store_bytes(ctx, l3_off + offsetof(struct iphdr, saddr), &nat->address, 4, 0); 635: (79) r1 = *(u64 *)(r10 -144) ; R1=ctx() R10=fp0 fp-144=ctx() 636: (b4) w2 = 26 ; R2=26 637: (b4) w4 = 4 ; R4=4 638: (b4) w5 = 0 ; R5=0 639: (85) call bpf_xdp_store_bytes#190 write into map forbidden, value_size=6 off=0 size=4 nat comes from a BPF_F_RDONLY_PROG map, so R3 is a PTR_TO_MAP_VALUE. The verifier checks the helper's memory access to R3 in check_mem_size_reg, as it reaches ARG_CONST_SIZE argument. The third argument has expected type ARG_PTR_TO_UNINIT_MEM, which includes the MEM_WRITE flag. The verifier thus checks for a BPF_WRITE access on R3. Given R3 points to a read-only map, the check fails. Conversely, ARG_PTR_TO_UNINIT_MEM can also lead to the helper reading from uninitialized memory. This patch simply fixes the expected argument type to match that of bpf_skb_store_bytes.
Timeline
ID reserved
By Linux
- 14 days later
· 14 days later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 3f364222d032eea6b245780e845ad213dab28cdd – < ffb5d1c5e3933b947fc7303ad68bf0c536d0c85e
- affected 3f364222d032eea6b245780e845ad213dab28cdd – < ddc34a1b85505c919026ddc82fafdada9a160b15
- affected 3f364222d032eea6b245780e845ad213dab28cdd – < 0db169a91381a473b7974021d1c02f8da72c5775
- affected 3f364222d032eea6b245780e845ad213dab28cdd – < d7b87adeb0eb539b9b824b101bb14fb01e41240b
- affected 3f364222d032eea6b245780e845ad213dab28cdd – < 57f7f6a0ad04a65c8a7a067b2f56cbbf2aec9e52
- affected 3f364222d032eea6b245780e845ad213dab28cdd – < 6557f1565d779851c4db9c488c49c05a47a6e72f
- affected 5.18
- unaffected < 5.18
- unaffected 6.1.165 – ≤ 6.1.*
- unaffected 6.6.128 – ≤ 6.6.*
- unaffected 6.12.75 – ≤ 6.12.*
- unaffected 6.18.14 – ≤ 6.18.*
- unaffected 6.19.4 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ffb5d1c5e3933b947fc7303ad68bf0c536d0c85e (opens in a new tab)
- https://git.kernel.org/stable/c/ddc34a1b85505c919026ddc82fafdada9a160b15 (opens in a new tab)
- https://git.kernel.org/stable/c/0db169a91381a473b7974021d1c02f8da72c5775 (opens in a new tab)
- https://git.kernel.org/stable/c/d7b87adeb0eb539b9b824b101bb14fb01e41240b (opens in a new tab)
- https://git.kernel.org/stable/c/57f7f6a0ad04a65c8a7a067b2f56cbbf2aec9e52 (opens in a new tab)
- https://git.kernel.org/stable/c/6557f1565d779851c4db9c488c49c05a47a6e72f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-32352 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-45886)Record last updated .