CVE-2026-53069net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: net, bpf: fix null-ptr-deref in xdp_master_redirect() for down master syzkaller reported a kernel panic in bond_rr_gen_slave_id() reached via xdp_master_redirect(). Full decoded trace: https://syzkaller.appspot.com/bug?extid=80e046b8da2820b6ba73 bond_rr_gen_slave_id() dereferences bond->rr_tx_counter, a per-CPU counter that bonding only allocates in bond_open() when the mode is round-robin. If the bond device was never brought up, rr_tx_counter stays NULL. The XDP redirect path can still reach that code on a bond that was never opened: bpf_master_redirect_enabled_key is a global static key, so as soon as any bond device has native XDP attached, the XDP_TX -> xdp_master_redirect() interception is enabled for every slave system-wide. The path xdp_master_redirect() -> bond_xdp_get_xmit_slave() -> bond_xdp_xmit_roundrobin_slave_get() -> bond_rr_gen_slave_id() then runs against a bond that has no rr_tx_counter and crashes. Fix this in the generic xdp_master_redirect() by refusing to call into the master's ->ndo_xdp_get_xmit_slave() when the master device is not up. IFF_UP is only set after ->ndo_open() has successfully returned, so this reliably excludes masters whose XDP state has not been fully initialized. Drop the frame with XDP_ABORTED so the exception is visible via trace_xdp_exception() rather than silently falling through. This is not specific to bonding: any current or future master that defers XDP state allocation to ->ndo_open() is protected.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Analyzed
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7 before 3128b294b426533c8d9162187446d93a8a160359; from 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7 before acbf45bd584d924b320bee2a7fe2a26f64904d95; 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7 builds before 866d3d9b87751b1944168fd82615505e0c0fd6cf; from 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7 before 183128da0406b1c10e6f60b7b9fe70788b9c8c1d; 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7 builds before 7bad93e99737e4a5c0c14ac50c05152cf4e28022; from 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7 before ea690b3b6e58ae00979af8195b4cc24df466b65e; from 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7 before 1921f91298d1388a0bb9db8f83800c998b649cb3 | CNA record |
linux linux_kernel linux:linux_kernel | from 5.15 before 5.15.209; from 5.16 before 6.1.175; from 6.2 before 6.6.141; from 6.7 before 6.12.91; from 6.13 before 6.18.33; from 6.19 before 7.0.10 | NVD |
References
- https://git.kernel.org/stable/c/3128b294b426533c8d9162187446d93a8a160359patch
- https://git.kernel.org/stable/c/acbf45bd584d924b320bee2a7fe2a26f64904d95patch
- https://git.kernel.org/stable/c/866d3d9b87751b1944168fd82615505e0c0fd6cfpatch
- https://git.kernel.org/stable/c/183128da0406b1c10e6f60b7b9fe70788b9c8c1dpatch
- https://git.kernel.org/stable/c/7bad93e99737e4a5c0c14ac50c05152cf4e28022patch
- https://git.kernel.org/stable/c/ea690b3b6e58ae00979af8195b4cc24df466b65epatch
- https://git.kernel.org/stable/c/1921f91298d1388a0bb9db8f83800c998b649cb3patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.