CyberSecBulletin
CVE-2026-23099NVD status: Modified

Linux: Out-of-bounds Read

Published Updated By the CyberSecBulletin desk

CVE-2026-23099 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 19266182b82e9100c799d8a29f5e0452f0bf7703, 72925dbb0c8c7b16bf922e93c6cc03cbd8c955c4, 5063b2cd9b27d35ab788d707d7858ded0acc8f1d as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 19266182b82e9100c799d8a29f5e0452f0bf7703 or 72925dbb0c8c7b16bf922e93c6cc03cbd8c955c4 or 5063b2cd9b27d35ab788d707d7858ded0acc8f1d or 80c881e53a4fa0a80fa4bef7bc0ead0e8e88940d, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 5.15.199 or 6.1.162 or 6.6.122 or 6.12.68, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux872254dd6b1f80cb95ee9e2e22980888533fc293 up to, but not including, 19266182b82e9100c799d8a29f5e0452f0bf7703; 872254dd6b1f80cb95ee9e2e22980888533fc293 up to, but not including, 72925dbb0c8c7b16bf922e93c6cc03cbd8c955c4; 872254dd6b1f80cb95ee9e2e22980888533fc293 up to, but not including, 5063b2cd9b27d35ab788d707d7858ded0acc8f1d; 872254dd6b1f80cb95ee9e2e22980888533fc293 up to, but not including, 80c881e53a4fa0a80fa4bef7bc0ead0e8e88940d; 872254dd6b1f80cb95ee9e2e22980888533fc293 up to, but not including, ef68afb1bee8d35a18896c27d7358079353d8d8a; 872254dd6b1f80cb95ee9e2e22980888533fc293 up to, but not including, 43dee6f7ef1d228821de1b61c292af3744c8d7da; 872254dd6b1f80cb95ee9e2e22980888533fc293 up to, but not including, c84fcb79e5dbde0b8d5aeeaf04282d2149aebcf6; 2.6.2419266182b82e9100c799d8a29f5e0452f0bf7703, 72925dbb0c8c7b16bf922e93c6cc03cbd8c955c4, 5063b2cd9b27d35ab788d707d7858ded0acc8f1d, 80c881e53a4fa0a80fa4bef7bc0ead0e8e88940d, ef68afb1bee8d35a18896c27d7358079353d8d8a, 43dee6f7ef1d228821de1b61c292af3744c8d7da
LinuxLinux Kernel2.6.24 up to, but not including, 5.15.199; 5.16 up to, but not including, 6.1.162; 6.2 up to, but not including, 6.6.122; 6.7 up to, but not including, 6.12.68; 6.13 up to, but not including, 6.18.8; 6.195.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.

Official description

In the Linux kernel, the following vulnerability has been resolved: bonding: limit BOND_MODE_8023AD to Ethernet devices BOND_MODE_8023AD makes sense for ARPHRD_ETHER only. syzbot reported: BUG: KASAN: global-out-of-bounds in __hw_addr_create net/core/dev_addr_lists.c:63 [inline] BUG: KASAN: global-out-of-bounds in __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118 Read of size 16 at addr ffffffff8bf94040 by task syz.1.3580/19497 CPU: 1 UID: 0 PID: 19497 Comm: syz.1.3580 Tainted: G L syzkaller #0 PREEMPT(full) Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: <TASK> dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 check_region_inline mm/kasan/generic.c:-1 [inline] kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:200 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105 __hw_addr_create net/core/dev_addr_lists.c:63 [inline] __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118 __dev_mc_add net/core/dev_addr_lists.c:868 [inline] dev_mc_add+0xa1/0x120 net/core/dev_addr_lists.c:886 bond_enslave+0x2b8b/0x3ac0 drivers/net/bonding/bond_main.c:2180 do_set_master+0x533/0x6d0 net/core/rtnetlink.c:2963 do_setlink+0xcf0/0x41c0 net/core/rtnetlink.c:3165 rtnl_changelink net/core/rtnetlink.c:3776 [inline] __rtnl_newlink net/core/rtnetlink.c:3935 [inline] rtnl_newlink+0x161c/0x1c90 net/core/rtnetlink.c:4072 rtnetlink_rcv_msg+0x7cf/0xb70 net/core/rtnetlink.c:6958 netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2550 netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline] netlink_unicast+0x82f/0x9e0 net/netlink/af_netlink.c:1344 netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1894 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 ____sys_sendmsg+0x505/0x820 net/socket.c:2592 ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2646 __sys_sendmsg+0x164/0x220 net/socket.c:2678 do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline] __do_fast_syscall_32+0x1dc/0x560 arch/x86/entry/syscall_32.c:307 do_fast_syscall_32+0x34/0x80 arch/x86/entry/syscall_32.c:332 entry_SYSENTER_compat_after_hwframe+0x84/0x8e </TASK> The buggy address belongs to the variable: lacpdu_mcast_addr+0x0/0x40

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that provides appropriate memory abstractions.

More Out-of-bounds Read vulnerabilities (CWE-125)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.