CVE Intelligence
Analysis AI-assisted

CVE-2026-53088: Linux kernel bcmgenet off-by-one in TX control block cleanup

CVE-2026-53088 is an off-by-one error in the bcmgenet network driver of the Linux kernel, where the transmit control block cleanup returns the wrong entry. The CNA assigns a CVSS 3.1 score of 9.8, and the record lists upstream fix commits across several stable branches. The record shows no CISA KEV listing and no confirmed exploitation in the sources consulted.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

CVE-2026-53088 is a flaw in the bcmgenet network driver of the Linux kernel. According to the record, the bcmgenet_put_txcb routine rewinds the transmit write pointer in the wrong order, so it returns a transmit control block (tx_cb) that is not the one being rewound during cleanup. The upstream fix rewinds the pointer first and then returns the entry it points to. The record classifies the weakness as CWE-193 (off-by-one error).

Impact

  • The CNA score is 9.8 (Critical) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, which describes a network-reachable issue requiring no privileges or user interaction, with high confidentiality, integrity and availability impact.
  • The record does not describe a concrete exploitation path or observed consequence, so the score should be read as the CNA's assessment.
  • Inference: incorrect cleanup of transmit control blocks can leave driver state inconsistent, which is consistent with the vendor treating it as a fix. The precise effect is not stated in the record.

Affected products and versions

The record lists the Linux Linux Kernel product with these ranges:

  • ≥ 3.16.50 e < 3.17
  • ≥ 4.13.1 e < 5.10.258
  • ≥ 5.11 e < 5.15.209
  • ≥ 5.16 e < 6.1.175
  • ≥ 6.2 e < 6.6.141
  • ≥ 6.7 e < 6.12.91
  • ≥ 6.13 e < 6.18.33
  • ≥ 6.19 e < 7.0.10
  • Version 4.13 and release candidates 4.13-rc2 through 4.13-rc7

The record does not state fixed versions explicitly. Inference: the upper bounds of the ranges suggest the first corrected releases on each branch, which should be confirmed against the upstream stable commits and your distribution's advisories.

Exploitation status

  • The record marks the vulnerability as not listed in CISA KEV, with no KEV dates and no EPSS score available.
  • No confirmed exploitation appears in the sources consulted.

Remediation and mitigation

  • Update to a stable kernel release on your branch that contains the upstream fix. The record lists fix commits for several stable lines.
  • For distribution kernels, follow the vendor's kernel advisories and verify that the installed package includes the backported patch.
  • The record does not describe a workaround. If patching is delayed, review whether the bcmgenet driver is in use on your systems and limit network exposure of those systems (inference).

Detection guidance

  • Compare the running kernel version with the ranges above, taking into account backports made by distribution vendors.
  • Maintain an inventory of systems that use the bcmgenet driver to prioritize patching.
  • Watch kernel logs and network interface behavior on affected systems for unexplained transmit errors or instability. This is a general recommendation, not a detection signature from the record.

Limitations of the available information

  • The record contains no exploit details, no vendor-specific advisory text, no hardware list and no workaround.
  • The record provides no CWE name and no title; the title used here is derived from the description.
  • The fixed version for each branch is not stated explicitly and must be verified.
  • The sources consulted include the CVE record and the NVD entry.

Frequently asked questions

Is CVE-2026-53088 known to be exploited?

The record shows it is not listed in CISA KEV, and no confirmed exploitation appears in the sources consulted.

Which kernels are affected?

The record lists several version ranges across stable branches, starting at 3.16.50 and including the 4.13 development series. Compare your kernel against the affected section and your vendor's advisories.

What should I do?

Apply the stable or vendor kernel update that includes the upstream fix, and verify backports in distribution kernels because the record does not state fixed versions explicitly.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.