Skip to main content
VulnerabilityPublished Updated

CVE-2026-53353: Linux kernel · hsr: Remove WARN_ONCE() in hsr_addr_is_self().

Source GCVE Database

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

A fix has been applied in the Linux kernel to remove the WARN_ONCE() call in hsr_addr_is_self(). Users should update to a Linux kernel version that includes this fix. Patch status is not explicitly provided, so users should consult the vendor or Linux kernel release notes for the specific fixed version.

Description

A vulnerability in the Linux kernel's hsr (High-availability Seamless Redundancy) module was addressed by removing a WARN_ONCE() call in the hsr_addr_is_self() function. The warning was triggered due to an incorrect assumption about the state of hsr->self_node during device removal, which could cause a kernel warning or soft lockup. This issue does not impact confidentiality or integrity but can cause an availability impact due to kernel warnings or potential soft lockups.

References

Community reviews

Loading reviews…