CVE-2026-53245

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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:

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr

In mrp_pdu_parse_vecattr(), vector attribute events are encoded three per byte and valen tracks the number of events left to process.

The parser decrements valen after processing the first and second events from each event byte, but not after processing the third one. When valen is exactly a multiple of three, the loop continues after the last valid event and consumes the next byte as a new event byte, applying a spurious event to the MRP applicant state.

Additionally, when valen is zero the parser unconditionally consumes attrlen bytes as FirstValue and advances the offset, even though per IEEE 802.1ak a VectorAttribute with only a LeaveAllEvent has valen of zero and no FirstValue or Vector fields. This corrupts the offset for subsequent PDU parsing.

Also, when valen exceeds three the loop crosses byte boundaries but the attribute value is not incremented between the last event of one byte and the first event of the next. This causes the first event of the next byte to use the same attribute value as the third event rather than the next consecutive value.

Decrement valen after processing the third event, skip FirstValue consumption when valen is zero, and increment the attribute value at the end of each loop iteration.

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
2%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 7, 2026

Advisory Details (8)

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

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7561c7fbc694308da73300f036719e63e42bf0b4
generic

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6eea6494e542a03cdf755a593b7d74f3f7c260fd
generic

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6d6e42e8e17f18d61327f8653479c5b5e161ae1d
generic

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/42446ca0f3570663e87183c065e0b4def52dfba2
generic

net/802/mrp: fix vector attribute parsing in mrp_pdu_parse_vecattr - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/36d259711872e3b2f6cd76a4d270c21931c0f35f

Vendor Advisories for CVE-2026-53245(2)

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

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
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 5× in last 7d / 62× 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 191 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-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:37 UTCEG score recompute
  11. 2026-08-30 19:37 UTCVendor advisory
  12. 2026-08-30 19:37 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-27 23:58 UTCEG score recompute
  17. 2026-08-27 23:58 UTCVendor advisory
  18. 2026-08-27 23:58 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 13:12 UTCEG score recompute
  23. 2026-08-24 13:12 UTCVendor advisory
  24. 2026-08-24 13:12 UTCGHSA enrichment
  25. 2026-08-23 10:37 UTCEG score recompute
Show 75 more
  1. 2026-08-23 10:37 UTCVendor advisory
  2. 2026-08-23 10:37 UTCGHSA enrichment
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-22 10:42 UTCEG score recompute
  5. 2026-08-22 10:42 UTCVendor advisory
  6. 2026-08-22 10:42 UTCGHSA enrichment
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 07:14 UTCEG score recompute
  9. 2026-08-21 07:14 UTCVendor advisory
  10. 2026-08-21 07:14 UTCGHSA enrichment
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 07:07 UTCEG score recompute
  13. 2026-08-20 07:07 UTCVendor advisory
  14. 2026-08-20 07:07 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 01:32 UTCEG score recompute
  17. 2026-08-19 01:32 UTCVendor advisory
  18. 2026-08-19 01:31 UTCGHSA enrichment
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 01:49 UTCEG score recompute
  22. 2026-08-17 01:49 UTCVendor advisory
  23. 2026-08-17 01:49 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:14 UTCEPSS rescore
  26. 2026-08-16 01:54 UTCVendor advisory
  27. 2026-08-16 01:54 UTCGHSA enrichment
  28. 2026-08-15 01:58 UTCEG score recompute
  29. 2026-08-15 01:58 UTCVendor advisory
  30. 2026-08-15 01:58 UTCGHSA enrichment
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-14 02:03 UTCEG score recompute
  33. 2026-08-14 02:03 UTCVendor advisory
  34. 2026-08-14 02:03 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 02:09 UTCEG score recompute
  37. 2026-08-13 02:09 UTCGHSA enrichment
  38. 2026-08-12 13:51 UTCEPSS rescore
  39. 2026-08-12 02:14 UTCEG score recompute
  40. 2026-08-12 02:14 UTCVendor advisory
  41. 2026-08-12 02:14 UTCGHSA enrichment
  42. 2026-08-11 02:19 UTCEG score recompute
  43. 2026-08-11 02:19 UTCVendor advisory
  44. 2026-08-11 02:19 UTCGHSA enrichment
  45. 2026-08-11 00:00 UTCEPSS rescore
  46. 2026-08-10 02:24 UTCEG score recompute
  47. 2026-08-10 02:24 UTCVendor advisory
  48. 2026-08-10 02:24 UTCGHSA enrichment
  49. 2026-08-09 13:46 UTCEPSS rescore
  50. 2026-08-09 02:29 UTCEG score recompute
  51. 2026-08-09 02:29 UTCVendor advisory
  52. 2026-08-09 02:29 UTCGHSA enrichment
  53. 2026-08-08 16:37 UTCEPSS rescore
  54. 2026-08-08 02:34 UTCEG score recompute
  55. 2026-08-08 02:34 UTCGHSA enrichment
  56. 2026-08-07 02:39 UTCEG score recompute
  57. 2026-08-07 02:39 UTCVendor advisory
  58. 2026-08-07 02:39 UTCGHSA enrichment
  59. 2026-08-06 13:47 UTCEPSS rescore
  60. 2026-08-06 02:44 UTCEG score recompute
  61. 2026-08-06 02:44 UTCVendor advisory
  62. 2026-08-06 02:44 UTCGHSA enrichment
  63. 2026-08-05 19:17 UTCEPSS rescore
  64. 2026-08-05 02:49 UTCEG score recompute
  65. 2026-08-05 02:49 UTCVendor advisory
  66. 2026-08-05 02:49 UTCGHSA enrichment
  67. 2026-08-04 15:10 UTCEPSS rescore
  68. 2026-08-04 10:39 UTCEPSS rescore
  69. 2026-08-04 02:55 UTCEG score recompute
  70. 2026-08-04 02:55 UTCGHSA enrichment
  71. 2026-08-03 10:36 UTCEPSS rescore
  72. 2026-08-03 03:00 UTCVendor advisory
  73. 2026-08-03 03:00 UTCGHSA enrichment
  74. 2026-08-02 03:05 UTCEG score recompute
  75. 2026-08-02 03:05 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-53245?
CVE-2026-53245 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net/802/mrp: fix vector attribute parsing in mrppduparse_vecattr In mrppduparse_vecattr(), vector attribute events are encoded three per byte and valen tracks the number of events left to process. The parser decrements valen after…
When was CVE-2026-53245 disclosed?
CVE-2026-53245 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53245 actively exploited?
CVE-2026-53245 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 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53245?
CVE-2026-53245 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53245, 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-53245

Explore →

Is Your Infrastructure Affected by CVE-2026-53245?

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