CVE-2026-53148

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.0Exploit: NoneExposed: 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:

thunderbolt: Clamp XDomain response data copy to allocation size

tb_xdp_properties_request() derives the per-packet copy length from the response header without checking that it fits in the previously allocated data buffer. A malicious peer can set its length field larger than the declared data_length, causing memcpy to write past the kcalloc allocation.

Clamp the per-packet copy length so that the cumulative offset never exceeds data_len.

CVSS v3
7.0
EG Score
7.0(high)
EPSS
3.7%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (10)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat.
redhat

2492756 – (CVE-2026-53148) CVE-2026-53148 kernel: thunderbolt: Clamp XDomain response data copy to allocation size

https://bugzilla.redhat.com/show_bug.cgi?id=2492756
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-53148
generic

thunderbolt: Clamp XDomain response data copy to allocation size - kernel/git/stable/linux.git - Linux kernel stable tree

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

thunderbolt: Clamp XDomain response data copy to allocation size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/906035d5c3784570191d259cbf9a0ac1617852b5
generic

thunderbolt: Clamp XDomain response data copy to allocation size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89ae04365e01d5ae4aae83044a8bbd2a9aaf8d0d
generic

thunderbolt: Clamp XDomain response data copy to allocation size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6021d39ccd979713b39b980286020d8f9a45efd1
generic

thunderbolt: Clamp XDomain response data copy to allocation size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5db10c8ad8c09f72c847dfeef3d876098257f505
generic

thunderbolt: Clamp XDomain response data copy to allocation size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/322e93448d908434ae5545660fcbe8f5a7a8e141
generic

thunderbolt: Clamp XDomain response data copy to allocation size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b334279a82d79fb4723bd4f614305de1ab69caa
generic

thunderbolt: Clamp XDomain response data copy to allocation size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05a43157676c243c248d1c6d9dcecbe6eba2f35d

Vendor Advisories for CVE-2026-53148(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 46× in last 7d / 58× 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.

  1. 2026-07-06 23:54 UTCEG score recompute
  2. 2026-07-06 23:54 UTCVendor advisory
  3. 2026-07-06 23:54 UTCGHSA enrichment
  4. 2026-07-06 12:13 UTCEG score recompute
  5. 2026-07-06 12:13 UTCVendor advisory
  6. 2026-07-06 12:13 UTCGHSA enrichment
  7. 2026-07-06 00:42 UTCEG score recompute
  8. 2026-07-06 00:42 UTCVendor advisory
  9. 2026-07-06 00:42 UTCGHSA enrichment
  10. 2026-07-05 13:10 UTCEG score recompute
  11. 2026-07-05 13:10 UTCVendor advisory
  12. 2026-07-05 13:10 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 01:38 UTCEG score recompute
  16. 2026-07-05 01:38 UTCVendor advisory
  17. 2026-07-05 01:38 UTCGHSA enrichment
  18. 2026-07-04 14:03 UTCEG score recompute
  19. 2026-07-04 14:03 UTCVendor advisory
  20. 2026-07-04 14:03 UTCGHSA enrichment
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 02:30 UTCEG score recompute
  24. 2026-07-04 02:30 UTCVendor advisory
  25. 2026-07-04 02:30 UTCGHSA enrichment
Show 33 more
  1. 2026-07-03 14:56 UTCEG score recompute
  2. 2026-07-03 14:56 UTCVendor advisory
  3. 2026-07-03 14:56 UTCGHSA enrichment
  4. 2026-07-03 03:23 UTCEG score recompute
  5. 2026-07-03 03:23 UTCVendor advisory
  6. 2026-07-03 03:22 UTCGHSA enrichment
  7. 2026-07-02 15:51 UTCEG score recompute
  8. 2026-07-02 15:51 UTCVendor advisory
  9. 2026-07-02 15:51 UTCGHSA enrichment
  10. 2026-07-02 04:19 UTCEG score recompute
  11. 2026-07-02 04:19 UTCVendor advisory
  12. 2026-07-02 04:19 UTCGHSA enrichment
  13. 2026-07-01 16:47 UTCEG score recompute
  14. 2026-07-01 16:47 UTCVendor advisory
  15. 2026-07-01 16:47 UTCGHSA enrichment
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 05:16 UTCEG score recompute▲ 7.00
  18. 2026-07-01 05:16 UTCVendor advisory
  19. 2026-07-01 05:16 UTCGHSA enrichment
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 04:34 UTCNVD updateCVSS v3 → 7 · severity → HIGH
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 07:42 UTCEG score recompute
  26. 2026-06-28 07:42 UTCVendor advisory
  27. 2026-06-28 07:42 UTCGHSA enrichment
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 04:56 UTCEPSS rescore
  30. 2026-06-27 03:08 UTCEPSS rescore
  31. 2026-06-25 13:49 UTCEPSS rescore
  32. 2026-06-25 10:08 UTCEG score recompute
  33. 2026-06-25 10:08 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53148?
CVE-2026-53148 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Clamp XDomain response data copy to allocation size tbxdpproperties_request() derives the per-packet copy length from the response header without checking that it fits in the previously allocated data buffer. A…
When was CVE-2026-53148 disclosed?
CVE-2026-53148 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53148 actively exploited?
CVE-2026-53148 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53148?
CVE-2026-53148 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-53148?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53148, 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

Explore the affected products and dependency analysis for CVE-2026-53148

Explore →

Is Your Infrastructure Affected by CVE-2026-53148?

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

Start Free Scan →Browse All CVEs