CVE-2025-71093Critical· 9.1▾ MidnightIn the Linux kernel, the following vulnerability has been resolved: e1000: fix OOB in e1000_tbi_should_accept() In e1000_tbi_should_accept() we read the last byte of the frame via 'data[length - 1]' to evaluate the TBI workaround. If t…
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 50.1 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 19.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.3%
In the Linux kernel, the following vulnerability has been resolved:
e1000: fix OOB in e1000_tbi_should_accept()
In e1000_tbi_should_accept() we read the last byte of the frame via 'data[length - 1]' to evaluate the TBI workaround. If the descriptor- reported length is zero or larger than the actual RX buffer size, this read goes out of bounds and can hit unrelated slab objects. The issue is observed from the NAPI receive path (e1000_clean_rx_irq):
================================================================== BUG: KASAN: slab-out-of-bounds in e1000_tbi_should_accept+0x610/0x790 Read of size 1 at addr ffff888014114e54 by task sshd/363
This happens because the TBI check unconditionally dereferences the last byte without validating the reported length first:
u8 last_byte = *(data + length - 1);
Fix by rejecting the frame early if the length is zero, or if it exceeds adapter->rx_buffer_len. This preserves the TBI workaround semantics for valid frames and prevents touching memory beyond the RX buffer.
Linux >= 2037110c96d5f1dd71453fcd0d54e79be12a352b < 4ccfa56f272241e8d8e2c38191fdbb03df489d80Linux >= 2037110c96d5f1dd71453fcd0d54e79be12a352b < 278b7cfe0d4da7502c7fd679b15032f014c92892Linux >= 2037110c96d5f1dd71453fcd0d54e79be12a352b < ad7a2a45e2417ac54089926b520924f8f0d91aeaLinux >= 2037110c96d5f1dd71453fcd0d54e79be12a352b < 2c4c0c09f9648ba766d399917d420d03e7b3e1f8Linux >= 2037110c96d5f1dd71453fcd0d54e79be12a352b < 26c8bebc2f25288c2bcac7bc0a7662279a0e817cLinux >= 2037110c96d5f1dd71453fcd0d54e79be12a352b < ee7c125fb3e8b04dd46510130b9fc92380e5d578Linux >= 2037110c96d5f1dd71453fcd0d54e79be12a352b < 9c72a5182ed92904d01057f208c390a303f00a0fLinux 3.18Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets