CVE-2026-53353

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

hsr: Remove WARN_ONCE() in hsr_addr_is_self().

syzbot reported the warning [0] in hsr_addr_is_self(), whose assumption is simply wrong.

hsr->self_node is cleared in hsr_del_self_node(), which is called from hsr_dellink().

Since dev->rtnl_link_ops->dellink() is called before unregister_netdevice_many(), there is a window when user can find the device but without hsr->self_node.

Let's remove WARN_ONCE() in hsr_addr_is_self().

[0]: HSR: No self node WARNING: net/hsr/hsr_framereg.c:39 at hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39, CPU#0: syz.4.16848/17220 Modules linked in: CPU: 0 UID: 0 PID: 17220 Comm: syz.4.16848 Tainted: G L syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 RIP: 0010:hsr_addr_is_self+0x211/0x3f0 net/hsr/hsr_framereg.c:39 Code: 33 2f 41 0f b7 dd 89 ee 09 de 31 ff e8 c8 b4 c6 f6 09 dd 74 54 e8 0f b0 c6 f6 31 ed eb 53 e8 06 b0 c6 f6 48 8d 3d 2f 50 9c 04 <67> 48 0f b9 3a 31 ed eb 42 e8 c1 13 1f 00 89 c5 31 ff 89 c6 e8 96 RSP: 0018:ffffc900041c70e0 EFLAGS: 00010283 RAX: ffffffff8afdc6ca RBX: ffffffff8afdc4e6 RCX: 0000000000080000 RDX: ffffc90010493000 RSI: 0000000000000948 RDI: ffffffff8f9a1700 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffffc900041c71e8 R11: fffff52000838e3f R12: dffffc0000000000 R13: ffff888041f9e3c0 R14: ffff888086ee3802 R15: 0000000000000000 FS: 00007f6fe985d6c0(0000) GS:ffff888126176000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f80bd437dac CR3: 0000000025096000 CR4: 00000000003526f0 DR0: ffffffffffffffff DR1: 00000000000001f8 DR2: 0000000000000002 DR3: ffffffffefffff15 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Call Trace: check_local_dest net/hsr/hsr_forward.c:592 [inline] fill_frame_info net/hsr/hsr_forward.c:728 [inline] hsr_forward_skb+0xa11/0x2a80 net/hsr/hsr_forward.c:739 hsr_dev_xmit+0x253/0x370 net/hsr/hsr_device.c:236 __netdev_start_xmit include/linux/netdevice.h:5368 [inline] netdev_start_xmit include/linux/netdevice.h:5377 [inline] xmit_one net/core/dev.c:3888 [inline] dev_hard_start_xmit+0x2df/0x860 net/core/dev.c:3904 __dev_queue_xmit+0x1428/0x3900 net/core/dev.c:4870 neigh_output include/net/neighbour.h:556 [inline] ip_finish_output2+0xcec/0x10b0 net/ipv4/ip_output.c:237 ip_send_skb net/ipv4/ip_output.c:1510 [inline] ip_push_pending_frames+0x8b/0x110 net/ipv4/ip_output.c:1530 raw_sendmsg+0x1547/0x1a50 net/ipv4/raw.c:659 sock_sendmsg_nosec net/socket.c:787 [inline] __sock_sendmsg net/socket.c:802 [inline] ____sys_sendmsg+0x7da/0x9c0 net/socket.c:2698 ___sys_sendmsg+0x2a5/0x360 net/socket.c:2752 __sys_sendmsg net/socket.c:2784 [inline] __do_sys_sendmsg net/socket.c:2789 [inline] __se_sys_sendmsg net/socket.c:2787 [inline] __x64_sys_sendmsg+0x1c3/0x2a0 net/socket.c:2787 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x15f/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6feb62ce59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6fe985d028 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f6feb8a6090 RCX: 00007f6feb62ce59 RDX: 0000000000000000 RSI: 0000200000000000 RDI: 0000000000000004 RBP: 00007f6feb6c2d6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6feb8a6128 R14: 00007f6feb8a6090 R15: 00007ffcf01cc488

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 22, 2026

Advisory Details (5)

Auto-updated Jul 22, 2026
No patch confirmed yet.
generic

hsr: Remove WARN_ONCE() in hsr_addr_is_self(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d71bb171661ec0225bf4babdd4d296d744982fb3
generic

hsr: Remove WARN_ONCE() in hsr_addr_is_self(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/afd0f17ca46258cec3a5cc48b8df9327fe772490
generic

hsr: Remove WARN_ONCE() in hsr_addr_is_self(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66a46e22396fd5d09606f37f73643eb20e99aa42
generic

hsr: Remove WARN_ONCE() in hsr_addr_is_self(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/271355c2ef6171dbc815e7ae653eed63444bbd58
generic

hsr: Remove WARN_ONCE() in hsr_addr_is_self(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0232b6fcb7615fb7fecfe0727a23065a53e228b8

Vendor Advisories for CVE-2026-53353(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Data Freshness Timeline

(refreshed 8× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 758 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-06 02:34 UTCEG score recompute
  7. 2026-09-06 02:34 UTCVendor advisory
  8. 2026-09-06 02:34 UTCGHSA enrichment
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:12 UTCEPSS rescore
  11. 2026-09-01 13:54 UTCEPSS rescore
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 13:14 UTCEG score recompute
  15. 2026-08-30 13:14 UTCVendor advisory
  16. 2026-08-30 13:14 UTCGHSA enrichment
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 22:28 UTCEG score recompute
  20. 2026-08-27 22:28 UTCVendor advisory
  21. 2026-08-27 22:28 UTCGHSA enrichment
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-24 10:55 UTCEG score recompute
Show 75 more
  1. 2026-08-24 10:55 UTCVendor advisory
  2. 2026-08-24 10:55 UTCGHSA enrichment
  3. 2026-08-23 07:29 UTCEG score recompute
  4. 2026-08-23 07:29 UTCVendor advisory
  5. 2026-08-23 07:28 UTCGHSA enrichment
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 07:22 UTCEG score recompute
  8. 2026-08-22 07:22 UTCVendor advisory
  9. 2026-08-22 07:22 UTCGHSA enrichment
  10. 2026-08-21 23:49 UTCEPSS rescore
  11. 2026-08-21 04:51 UTCEG score recompute
  12. 2026-08-21 04:51 UTCVendor advisory
  13. 2026-08-21 04:51 UTCGHSA enrichment
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 04:46 UTCEG score recompute
  16. 2026-08-20 04:46 UTCGHSA enrichment
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 23:38 UTCEG score recompute
  19. 2026-08-18 23:38 UTCVendor advisory
  20. 2026-08-18 23:38 UTCGHSA enrichment
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 23:33 UTCVendor advisory
  23. 2026-08-17 23:33 UTCGHSA enrichment
  24. 2026-08-16 20:45 UTCEG score recompute
  25. 2026-08-16 20:45 UTCVendor advisory
  26. 2026-08-16 20:45 UTCGHSA enrichment
  27. 2026-08-16 14:56 UTCEPSS rescore
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 20:40 UTCEG score recompute
  30. 2026-08-15 20:40 UTCVendor advisory
  31. 2026-08-15 20:40 UTCGHSA enrichment
  32. 2026-08-15 01:30 UTCEPSS rescore
  33. 2026-08-14 20:35 UTCEG score recompute
  34. 2026-08-14 20:35 UTCVendor advisory
  35. 2026-08-14 20:35 UTCGHSA enrichment
  36. 2026-08-13 22:00 UTCEPSS rescore
  37. 2026-08-13 20:29 UTCVendor advisory
  38. 2026-08-13 20:29 UTCGHSA enrichment
  39. 2026-08-12 20:16 UTCEG score recompute
  40. 2026-08-12 20:16 UTCVendor advisory
  41. 2026-08-12 20:16 UTCGHSA enrichment
  42. 2026-08-12 13:51 UTCEPSS rescore
  43. 2026-08-11 20:11 UTCEG score recompute
  44. 2026-08-11 20:11 UTCVendor advisory
  45. 2026-08-11 20:11 UTCGHSA enrichment
  46. 2026-08-11 00:00 UTCEPSS rescore
  47. 2026-08-10 20:07 UTCGHSA enrichment
  48. 2026-08-09 20:02 UTCEG score recompute
  49. 2026-08-09 20:02 UTCGHSA enrichment
  50. 2026-08-09 13:46 UTCEPSS rescore
  51. 2026-08-08 19:58 UTCEG score recompute
  52. 2026-08-08 19:58 UTCVendor advisory
  53. 2026-08-08 19:58 UTCGHSA enrichment
  54. 2026-08-08 16:37 UTCEPSS rescore
  55. 2026-08-07 19:53 UTCEG score recompute
  56. 2026-08-07 19:53 UTCGHSA enrichment
  57. 2026-08-06 19:49 UTCEG score recompute
  58. 2026-08-06 19:49 UTCVendor advisory
  59. 2026-08-06 19:49 UTCGHSA enrichment
  60. 2026-08-06 13:47 UTCEPSS rescore
  61. 2026-08-05 19:44 UTCEG score recompute
  62. 2026-08-05 19:44 UTCVendor advisory
  63. 2026-08-05 19:44 UTCGHSA enrichment
  64. 2026-08-05 19:17 UTCEPSS rescore
  65. 2026-08-04 19:40 UTCEG score recompute
  66. 2026-08-04 19:40 UTCVendor advisory
  67. 2026-08-04 19:40 UTCGHSA enrichment
  68. 2026-08-04 15:10 UTCEPSS rescore
  69. 2026-08-04 10:39 UTCEPSS rescore
  70. 2026-08-03 19:33 UTCEG score recompute
  71. 2026-08-03 19:33 UTCVendor advisory
  72. 2026-08-03 19:33 UTCGHSA enrichment
  73. 2026-08-03 10:36 UTCEPSS rescore
  74. 2026-08-02 19:29 UTCEG score recompute
  75. 2026-08-02 19:29 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-53353?
CVE-2026-53353 is a medium vulnerability published on July 1, 2026. In the Linux kernel, the following vulnerability has been resolved: hsr: Remove WARNONCE() in hsraddrisself(). syzbot reported the warning [0] in hsraddris_self(), whose assumption is simply wrong. hsr->selfnode is cleared in hsrdelselfnode(), which is called from hsr_dellink(). Since…
When was CVE-2026-53353 disclosed?
CVE-2026-53353 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53353 actively exploited?
CVE-2026-53353 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53353?
CVE-2026-53353 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53353?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53353, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53353

Explore →

Is Your Infrastructure Affected by CVE-2026-53353?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs