{
  "threat_severity" : "Moderate",
  "public_date" : "2026-02-14T00:00:00Z",
  "bugzilla" : {
    "description" : "kernel: Linux kernel: Use-after-free in bonding module can cause system crash or arbitrary code execution",
    "id" : "2439886",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2439886"
  },
  "cvss3" : {
    "cvss3_base_score" : "7.0",
    "cvss3_scoring_vector" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H",
    "status" : "verified"
  },
  "cwe" : "CWE-416",
  "details" : [ "In the Linux kernel, the following vulnerability has been resolved:\nbonding: fix use-after-free due to enslave fail after slave array update\nFix a use-after-free which happens due to enslave failure after the new\nslave has been added to the array. Since the new slave can be used for Tx\nimmediately, we can use it after it has been freed by the enslave error\ncleanup path which frees the allocated slave memory. Slave update array is\nsupposed to be called last when further enslave failures are not expected.\nMove it after xdp setup to avoid any problems.\nIt is very easy to reproduce the problem with a simple xdp_pass prog:\nip l add bond1 type bond mode balance-xor\nip l set bond1 up\nip l set dev bond1 xdp object xdp_pass.o sec xdp_pass\nip l add dumdum type dummy\nThen run in parallel:\nwhile :; do ip l set dumdum master bond1 1>/dev/null 2>&1; done;\nmausezahn bond1 -a own -b rand -A rand -B 1.1.1.1 -c 0 -t tcp \"dp=1-1023, flags=syn\"\nThe crash happens almost immediately:\n[  605.602850] Oops: general protection fault, probably for non-canonical address 0xe0e6fc2460000137: 0000 [#1] SMP KASAN NOPTI\n[  605.602916] KASAN: maybe wild-memory-access in range [0x07380123000009b8-0x07380123000009bf]\n[  605.602946] CPU: 0 UID: 0 PID: 2445 Comm: mausezahn Kdump: loaded Tainted: G    B               6.19.0-rc6+ #21 PREEMPT(voluntary)\n[  605.602979] Tainted: [B]=BAD_PAGE\n[  605.602998] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  605.603032] RIP: 0010:netdev_core_pick_tx+0xcd/0x210\n[  605.603063] Code: 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 3e 01 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 6b 08 49 8d 7d 30 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 25 01 00 00 49 8b 45 30 4c 89 e2 48 89 ee 48 89\n[  605.603111] RSP: 0018:ffff88817b9af348 EFLAGS: 00010213\n[  605.603145] RAX: dffffc0000000000 RBX: ffff88817d28b420 RCX: 0000000000000000\n[  605.603172] RDX: 00e7002460000137 RSI: 0000000000000008 RDI: 07380123000009be\n[  605.603199] RBP: ffff88817b541a00 R08: 0000000000000001 R09: fffffbfff3ed8c0c\n[  605.603226] R10: ffffffff9f6c6067 R11: 0000000000000001 R12: 0000000000000000\n[  605.603253] R13: 073801230000098e R14: ffff88817d28b448 R15: ffff88817b541a84\n[  605.603286] FS:  00007f6570ef67c0(0000) GS:ffff888221dfa000(0000) knlGS:0000000000000000\n[  605.603319] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  605.603343] CR2: 00007f65712fae40 CR3: 000000011371b000 CR4: 0000000000350ef0\n[  605.603373] Call Trace:\n[  605.603392]  <TASK>\n[  605.603410]  __dev_queue_xmit+0x448/0x32a0\n[  605.603434]  ? __pfx_vprintk_emit+0x10/0x10\n[  605.603461]  ? __pfx_vprintk_emit+0x10/0x10\n[  605.603484]  ? __pfx___dev_queue_xmit+0x10/0x10\n[  605.603507]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n[  605.603546]  ? _printk+0xcb/0x100\n[  605.603566]  ? __pfx__printk+0x10/0x10\n[  605.603589]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n[  605.603627]  ? add_taint+0x5e/0x70\n[  605.603648]  ? add_taint+0x2a/0x70\n[  605.603670]  ? end_report.cold+0x51/0x75\n[  605.603693]  ? bond_start_xmit+0xbfb/0xc20 [bonding]\n[  605.603731]  bond_start_xmit+0x623/0xc20 [bonding]", "A flaw was found in the Linux kernel's bonding module. This use-after-free vulnerability occurs when a new slave device is added to the bonding array but fails during the enslave process. A local attacker can exploit this by triggering the enslave failure, which may lead to a system crash, resulting in a Denial of Service (DoS), or potentially allow for arbitrary code execution." ],
  "affected_release" : [ {
    "product_name" : "Red Hat Enterprise Linux 10",
    "release_date" : "2026-04-06T00:00:00Z",
    "advisory" : "RHSA-2026:6632",
    "cpe" : "cpe:/o:redhat:enterprise_linux:10.1",
    "package" : "kernel-0:6.12.0-124.49.1.el10_1"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "release_date" : "2026-03-30T00:00:00Z",
    "advisory" : "RHSA-2026:6153",
    "cpe" : "cpe:/a:redhat:enterprise_linux:9",
    "package" : "kernel-0:5.14.0-611.45.1.el9_7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "release_date" : "2026-03-30T00:00:00Z",
    "advisory" : "RHSA-2026:6153",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9",
    "package" : "kernel-0:5.14.0-611.45.1.el9_7"
  } ],
  "package_state" : [ {
    "product_name" : "Red Hat Enterprise Linux 6",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:6"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 7",
    "fix_state" : "Not affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:7"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Not affected",
    "package_name" : "kernel",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 8",
    "fix_state" : "Not affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:8"
  }, {
    "product_name" : "Red Hat Enterprise Linux 9",
    "fix_state" : "Affected",
    "package_name" : "kernel-rt",
    "cpe" : "cpe:/o:redhat:enterprise_linux:9"
  } ],
  "references" : [ "https://www.cve.org/CVERecord?id=CVE-2026-23171\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-23171\nhttps://lore.kernel.org/linux-cve-announce/2026021421-CVE-2026-23171-5a73@gregkh/T" ],
  "name" : "CVE-2026-23171",
  "mitigation" : {
    "value" : "To mitigate this issue, prevent the `bonding` kernel module from loading if bonding interfaces are not required. This can be achieved by creating a modprobe configuration file.\nCreate a file named `/etc/modprobe.d/disable-bonding.conf` with the following content:\n`install bonding /bin/true`\nAfter creating the file, a system reboot is required for the change to take effect if the module is currently loaded. This action will prevent the creation and use of bonding network interfaces.",
    "lang" : "en:us"
  },
  "csaw" : false
}