CVE-2025-71093
Severity CVSS v4.0:
Pending analysis
Type:
Unavailable / Other
Publication date:
13/01/2026
Last modified:
13/01/2026
Description
In the Linux kernel, the following vulnerability has been resolved:<br />
<br />
e1000: fix OOB in e1000_tbi_should_accept()<br />
<br />
In e1000_tbi_should_accept() we read the last byte of the frame via<br />
&#39;data[length - 1]&#39; to evaluate the TBI workaround. If the descriptor-<br />
reported length is zero or larger than the actual RX buffer size, this<br />
read goes out of bounds and can hit unrelated slab objects. The issue<br />
is observed from the NAPI receive path (e1000_clean_rx_irq):<br />
<br />
==================================================================<br />
BUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790<br />
Read of size 1 at addr ffff888014114e54 by task sshd/363<br />
<br />
CPU: 0 PID: 363 Comm: sshd Not tainted 5.18.0-rc1 #1<br />
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org 04/01/2014<br />
Call Trace:<br />
<br />
dump_stack_lvl+0x5a/0x74<br />
print_address_description+0x7b/0x440<br />
print_report+0x101/0x200<br />
kasan_report+0xc1/0xf0<br />
e1000_tbi_should_accept+0x610/0x790<br />
e1000_clean_rx_irq+0xa8c/0x1110<br />
e1000_clean+0xde2/0x3c10<br />
__napi_poll+0x98/0x380<br />
net_rx_action+0x491/0xa20<br />
__do_softirq+0x2c9/0x61d<br />
do_softirq+0xd1/0x120<br />
<br />
<br />
__local_bh_enable_ip+0xfe/0x130<br />
ip_finish_output2+0x7d5/0xb00<br />
__ip_queue_xmit+0xe24/0x1ab0<br />
__tcp_transmit_skb+0x1bcb/0x3340<br />
tcp_write_xmit+0x175d/0x6bd0<br />
__tcp_push_pending_frames+0x7b/0x280<br />
tcp_sendmsg_locked+0x2e4f/0x32d0<br />
tcp_sendmsg+0x24/0x40<br />
sock_write_iter+0x322/0x430<br />
vfs_write+0x56c/0xa60<br />
ksys_write+0xd1/0x190<br />
do_syscall_64+0x43/0x90<br />
entry_SYSCALL_64_after_hwframe+0x44/0xae<br />
RIP: 0033:0x7f511b476b10<br />
Code: 73 01 c3 48 8b 0d 88 d3 2b 00 f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 83 3d f9 2b 2c 00 00 75 10 b8 01 00 00 00 0f 05 3d 01 f0 ff ff 73 31 c3 48 83 ec 08 e8 8e 9b 01 00 48 89 04 24<br />
RSP: 002b:00007ffc9211d4e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001<br />
RAX: ffffffffffffffda RBX: 0000000000004024 RCX: 00007f511b476b10<br />
RDX: 0000000000004024 RSI: 0000559a9385962c RDI: 0000000000000003<br />
RBP: 0000559a9383a400 R08: fffffffffffffff0 R09: 0000000000004f00<br />
R10: 0000000000000070 R11: 0000000000000246 R12: 0000000000000000<br />
R13: 00007ffc9211d57f R14: 0000559a9347bde7 R15: 0000000000000003<br />
<br />
Allocated by task 1:<br />
__kasan_krealloc+0x131/0x1c0<br />
krealloc+0x90/0xc0<br />
add_sysfs_param+0xcb/0x8a0<br />
kernel_add_sysfs_param+0x81/0xd4<br />
param_sysfs_builtin+0x138/0x1a6<br />
param_sysfs_init+0x57/0x5b<br />
do_one_initcall+0x104/0x250<br />
do_initcall_level+0x102/0x132<br />
do_initcalls+0x46/0x74<br />
kernel_init_freeable+0x28f/0x393<br />
kernel_init+0x14/0x1a0<br />
ret_from_fork+0x22/0x30<br />
The buggy address belongs to the object at ffff888014114000<br />
which belongs to the cache kmalloc-2k of size 2048<br />
The buggy address is located 1620 bytes to the right of<br />
2048-byte region [ffff888014114000, ffff888014114800]<br />
The buggy address belongs to the physical page:<br />
page:ffffea0000504400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x14110<br />
head:ffffea0000504400 order:3 compound_mapcount:0 compound_pincount:0<br />
flags: 0x100000000010200(slab|head|node=0|zone=1)<br />
raw: 0100000000010200 0000000000000000 dead000000000001 ffff888013442000<br />
raw: 0000000000000000 0000000000080008 00000001ffffffff 0000000000000000<br />
page dumped because: kasan: bad access detected<br />
==================================================================<br />
<br />
This happens because the TBI check unconditionally dereferences the last<br />
byte without validating the reported length first:<br />
<br />
u8 last_byte = *(data + length - 1);<br />
<br />
Fix by rejecting the frame early if the length is zero, or if it exceeds<br />
adapter->rx_buffer_len. This preserves the TBI workaround semantics for<br />
valid frames and prevents touching memory beyond the RX buffer.
Impact
References to Advisories, Solutions, and Tools
- https://git.kernel.org/stable/c/26c8bebc2f25288c2bcac7bc0a7662279a0e817c
- https://git.kernel.org/stable/c/2c4c0c09f9648ba766d399917d420d03e7b3e1f8
- https://git.kernel.org/stable/c/9c72a5182ed92904d01057f208c390a303f00a0f
- https://git.kernel.org/stable/c/ad7a2a45e2417ac54089926b520924f8f0d91aea
- https://git.kernel.org/stable/c/ee7c125fb3e8b04dd46510130b9fc92380e5d578



