Skip to main content
VulnerabilityPublished Updated

CVE-2026-53069: Linux kernel · NULL Pointer Dereference

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in ea690b3b6e58ae00979af8195b4cc24df466b65e : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in ea690b3b6e58ae00979af8195b4cc24df466b65e, acbf45bd584d924b320bee2a7fe2a26f64904d95, 183128da0406b1c10e6f60b7b9fe70788b9c8c1d +4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7, < ea690b3b6e58ae00979af8195b4cc24df466b65e
Fixed in
  • ea690b3b6e58ae00979af8195b4cc24df466b65e
LinuxLinuxAffected
  • ≥ 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7, < acbf45bd584d924b320bee2a7fe2a26f64904d95
Fixed in
  • acbf45bd584d924b320bee2a7fe2a26f64904d95
LinuxLinuxAffected
  • ≥ 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7, < 183128da0406b1c10e6f60b7b9fe70788b9c8c1d
Fixed in
  • 183128da0406b1c10e6f60b7b9fe70788b9c8c1d
LinuxLinuxAffected
  • ≥ 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7, < 3128b294b426533c8d9162187446d93a8a160359
Fixed in
  • 3128b294b426533c8d9162187446d93a8a160359
LinuxLinuxAffected
  • ≥ 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7, < 1921f91298d1388a0bb9db8f83800c998b649cb3
Fixed in
  • 1921f91298d1388a0bb9db8f83800c998b649cb3
LinuxLinuxAffected
  • ≥ 879af96ffd72706c6e3278ea6b45b0b0e37ec5d7, < 866d3d9b87751b1944168fd82615505e0c0fd6cf
Fixed in
  • 866d3d9b87751b1944168fd82615505e0c0fd6cf

Description

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.

References

Community reviews

Loading reviews…