CVE-2026-80988

NTB: ntb_transport: Fail TX enqueue when the QP link is down

N/A
Published: September 11, 2026 at 07:42 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: NTB: ntb_transport: Fail TX enqueue when the QP link is down Commit f195a1a6fe41 ("ntb: Drop packets when qp link is down") meant to make ntb_transport_tx_enqueue() drop packets submitted while the QP link is down, but it only returns 0 without consuming the packet. Zero means success by this function's contract, so ntb_netdev reports NETDEV_TX_OK and forgets the skb: nothing queued it, nothing frees it, and it leaks, one skb for every transmit racing a link-down. Return -ENOLINK instead, restoring the contract that a non-zero return leaves the buffer owned by the caller. With the preceding patch, ntb_netdev frees the skb on non-retryable enqueue failures and returns NETDEV_TX_OK, so a packet racing with link-down is dropped without leaking or entering a busy retry loop.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3cfdc448e8bfa8a7eaa5af87f357330566124b784.14.3264.19.295449b1978d4e50b14b2a4de3a26d0b074593926a34f4af6b8b7a23fa37decaf43b55403e6bfd8e2195.10.1955.15.1325.4.2576.1.536.4.166.5.36.694491412a2afc8a5aea4c5b455aed86d3486f0b1a8986a61ebee0b54c5d648444fbae09bd1c6dcd2aa6d6ed213b62cbdb09ea32abbfa085dd987a0c9bfa051f650a7708183bd86901ca4645dcf88c486c2cd5d993f57f819d46fe62387d3cc34d8468e60f195a1a6fe416882984f8bd6c61afc1383171860
Vendor states this is fixed in 45cc11035165918dd1f81796ea98f81ece20d361 (fixed)
Vendor states this is fixed in 5eca0d899a3be661a7e2caaaa7467a6fa15d756c (fixed)
Vendor states this is fixed in 76c9ccc0c6bebfc74c0e727eda67687f5103ab06 (fixed)
Vendor states this is fixed in 873ce713fef5dde0939220f04f3484ec86a16fba (fixed)
Vendor states this is fixed in 89177732fe1653bbfef10cf5d99bf20cf57762c2 (fixed)
Vendor states this is fixed in 894e136b432da75c0352c80299807a5c4b04f167 (fixed)
Vendor states this is fixed in 96d792c65b9d5f7f9dd86a1004315db59e450c07 (fixed)
Vendor states this is fixed in e6cc541fab01099fd8efadfa4f13afdf118bf536 (fixed)
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Affected range stops below 6.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card