CVE-2026-52927

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

netfilter: ebtables: fix OOB read in compat_mtw_from_user

Luxiao Xu says:

The function compat_mtw_from_user() converts ebtables extensions from 32-bit user structures to kernel native structures. However, it lacks proper validation of the user-supplied match_size/target_size.

When certain extensions are processed, the kernel-side translation logic may perform memory accesses based on the extension's expected size. If the user provides a size smaller than what the extension requires, it results in an out-of-bounds read as reported by KASAN.

This fix introduces a check to ensure match_size is at least as large as the extension's required compatsize. This covers matches, watchers, and targets, while maintaining compatibility with standard targets.

AFAIU this is relevant for matches that need to go though match->compat_from_user() call. Those that use plain memcpy with the user-provided size are ok because the caller checks that size vs the start of the next rule entry offset (which itself is checked vs. total size copied from userspace).

The ->compat_from_user() callbacks assume they can read compatsize bytes, so they need this extra check.

Based on an earlier patch from Luxiao Xu.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

netfilter: ebtables: fix OOB read in compat_mtw_from_user - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: ebtables: fix OOB read in compat_mtw_from_user - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: ebtables: fix OOB read in compat_mtw_from_user - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: ebtables: fix OOB read in compat_mtw_from_user - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: ebtables: fix OOB read in compat_mtw_from_user - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: ebtables: fix OOB read in compat_mtw_from_user - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: ebtables: fix OOB read in compat_mtw_from_user - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ad0e463fc7eafae2141cc38054264636f8b3e94
generic

netfilter: ebtables: fix OOB read in compat_mtw_from_user - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21af4c030567d2e6c89bb927bc18b51fba52a400

Vendor Advisories for CVE-2026-52927(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

(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 (141 versions)7.0.12-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(8)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-52927?
CVE-2026-52927 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: fix OOB read in compatmtwfrom_user Luxiao Xu says: The function compatmtwfrom_user() converts ebtables extensions from 32-bit user structures to kernel native structures. However, it lacks proper validation of…
When was CVE-2026-52927 disclosed?
CVE-2026-52927 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52927 actively exploited?
CVE-2026-52927 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-52927?
CVE-2026-52927 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-52927?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52927, 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-52927

Explore →

Is Your Infrastructure Affected by CVE-2026-52927?

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