CVE-2026-53148

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
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:

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

Published

June 25, 2026

Last Modified

July 15, 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.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1010.10) @ resolute2026-08-30ubuntu

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 (145 versions)7.0.13-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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 July 15, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 91.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53148?
CVE-2026-53148 has a CVSS v3 base score of 7.8 (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

See which npm, PyPI, Go, and Maven packages are affected by 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