CYBERSECURITYTRACKER
TRACKING7,103 stories in this site build1,503 vulnerability news stories in this site build
Vulnerabilities

CVE-2026-53266

Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker data as of: .

Detection and validation

Mapped metadata availability only. These signals do not change priority.

  • Sigma

    Not mapped by tracked sources.

  • Atomic

    Not mapped by tracked sources.

  • Nuclei

    Not mapped by tracked sources.

  • Metasploit

    Not mapped by tracked sources.

What it is

Reported

Linux Kernel contains an out-of-bounds write vulnerability in the ebtables SNAT target which allows an ARP sender hardware address rewrite to write directly into a nonlinear socket-buffer fragment backed by a splice-imported file page. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.

Source reported · Source: Tracked source · Source last published: unknown · Source description excerpt; complete tracked detail loads below. · Source last updated: · Tracker data as of:

What is affected

Reported

Linux; Kernel. Product-level identification only; no affected-version conclusion is available from this field.

Source reported · Source: Tracked source · Source last published: unknown · Source last updated: · Tracker data as of:

Urgency and basis

Reported

Act · 446.4

Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated: · Tracker data as of:

Exploitation evidence

Reported

listed by a tracked exploitation catalog · CISA KEV · VulnCheck KEV · ENISA exploited-vulnerability catalog

Source reported · CISA KEV added: · VulnCheck KEV added: · ENISA added: · Source last updated: · Tracker data as of:

What to do

Reported

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Source reported · Tracked source remediation field · Source last updated: · Tracker data as of:

Evidence detail

Loading the full tracker evidence record…

Glossary

Open in glossary