CVE-2026-53069·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.10
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.38% — higher than 32% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-53069 scores 7.5 on CVSS, so a successful attack would be serious — but at 0.38%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.10
Fixed in: 7.0.10
How to fix this CVE
Update your Linux kernel to version 7.0.10 or later to resolve a null pointer dereference vulnerability in the XDP master redirect code path. This vulnerability affects systems using bonded network interfaces with XDP attached, potentially causing kernel panics. Apply the kernel patch immediately through your distribution's package manager to prevent denial of service conditions.
sudo dnf update kernel kernel-headers kernel-develDefensia detects this vulnerability
How to check if you are affected
- Check your installed kernel version: uname -r | grep -E '^(6\.19|6\.2[0-9]|7\.0\.[0-9])'
- Verify if bonded network interfaces with XDP are active: cat /proc/net/bonding/* && ethtool -i $(ip link show | grep bond | awk '{print $2}' | cut -d: -f1) | grep xdp
- Search kernel logs for XDP-related crashes: journalctl -b | grep -i 'xdp\|bond_rr_gen\|null.*ptr'
- Confirm kernel patch applied: grep 'xdp_master_redirect' /boot/System.map-$(uname -r) && verify version is >= 7.0.10 with uname -r
FAQ
What is CVE-2026-53069?
A null pointer dereference in the Linux kernel's XDP (eXpress Data Path) master redirect function that can be triggered when XDP is attached to bonded network interfaces, causing kernel panics on systems with bond devices that were never brought online.
Is CVE-2026-53069 being actively exploited?
No, there are no known active exploits or public proof-of-concept code available. This vulnerability requires specific network configuration (bonded interfaces with XDP) and is not listed in CISA's Known Exploited Vulnerabilities catalog.
What versions of Kernel are affected by CVE-2026-53069?
Linux kernel versions 6.19 through 7.0.9 are vulnerable. Version 7.0.10 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-53069?
Run 'uname -r' to check your kernel version—if it shows 6.19.x through 7.0.9, you're vulnerable. Additionally, check if bonded interfaces are configured with 'cat /proc/net/bonding/*' to determine exposure.
Does Defensia detect CVE-2026-53069?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-53069 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/183128da0406b1c10e6f60b7b9fe70788b9c8c1d
- https://git.kernel.org/stable/c/1921f91298d1388a0bb9db8f83800c998b649cb3
- https://git.kernel.org/stable/c/3128b294b426533c8d9162187446d93a8a160359
- https://git.kernel.org/stable/c/7bad93e99737e4a5c0c14ac50c05152cf4e28022
- https://git.kernel.org/stable/c/866d3d9b87751b1944168fd82615505e0c0fd6cf
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-53069. Free for 1 server.
Get started free