CVE-2026-46153

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-05-28.

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

A fix is available — apply it.

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

8021q: delete cleared egress QoS mappings

vlan_dev_set_egress_priority() currently keeps cleared egress priority mappings in the hash as tombstones. Repeated set/clear cycles with distinct skb priorities therefore accumulate mapping nodes until device teardown and leak memory.

Delete mappings when vlan_prio is cleared instead of keeping tombstones. Now that the egress mapping lists are RCU protected, the node can be unlinked safely and freed after a grace period.

CVSS v3
EG Score
5.5(low)
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

May 28, 2026

Last Modified

June 14, 2026

Advisory Details (2)

Auto-updated Jun 13, 2026
No patch confirmed yet.
generic

8021q: delete cleared egress QoS mappings - kernel/git/stable/linux.git - Linux kernel stable tree

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

8021q: delete cleared egress QoS mappings - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7dddc74af369478ba7f9bc136d0fc1dc4570cb66

Vendor Advisories for CVE-2026-46153(2)

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

Patch Availability(8)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 4× in last 7d / 64× 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 188 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2026-46153?
CVE-2026-46153 is a medium vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: 8021q: delete cleared egress QoS mappings vlandevsetegresspriority() currently keeps cleared egress priority mappings in the hash as tombstones. Repeated set/clear cycles with distinct skb priorities therefore accumulate mapping…
When was CVE-2026-46153 disclosed?
CVE-2026-46153 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46153 actively exploited?
CVE-2026-46153 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 98.5% of all scored CVEs.
How do I remediate CVE-2026-46153?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46153, 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-46153

Explore →

Is Your Infrastructure Affected by CVE-2026-46153?

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