Skip to main content

Linux Kernel CVE-2026-53149

| EUVDEUVD-2026-39240 HIGH
Out-of-bounds Read (CWE-125)
2026-06-25 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-4463-xxf2-768j
7.1
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
7.1 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
vuln.today AI
7.1 HIGH

Out-of-bounds read triggered by device-supplied property data on a Thunderbolt-enabled host yields memory disclosure (C:H) and kernel crash (A:H), no integrity impact; kept AV:L per NVD though a peripheral AV:P model is plausible.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 06, 2026 - 20:01 vuln.today
CVSS changed
Jul 06, 2026 - 17:52 NVD
7.1 (HIGH)
Patch available
Jun 25, 2026 - 10:32 EUVD
CVE Published
Jun 25, 2026 - 09:16 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 25, 2026 - 09:16 nvd
HIGH 7.1

DescriptionNVD

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

thunderbolt: Bound root directory content to block size

__tb_property_parse_dir() does not check that content_offset + content_len fits within block_len for the root directory case. When rootdir->length equals or exceeds block_len - 2, the entry loop reads past the allocated property block.

Add a bounds check after computing content_offset and content_len to reject directories whose content extends past the block.

AnalysisAI

Out-of-bounds read in the Linux kernel Thunderbolt (thunderbolt) property parser lets a crafted property directory from a connected Thunderbolt/USB4 device cause the kernel to read past an allocated property block, potentially disclosing adjacent kernel memory or crashing the system. The flaw lives in __tb_property_parse_dir(), which fails to validate that content_offset + content_len stays within block_len for the root directory. It affects a broad range of stable kernel series and is fixed upstream; there is no public exploit identified at time of analysis, and EPSS exploitation probability is low at 0.18% (7th percentile).

Technical ContextAI

The affected component is the kernel's Thunderbolt/USB4 subsystem, specifically the ICM/XDomain property-directory parser used to interpret the DROM-like property blocks that a connected Thunderbolt device or peer host advertises. In __tb_property_parse_dir(), the code computes content_offset and content_len for the root directory but does not verify these values fall within block_len before iterating entries; when rootdir->length is at least block_len - 2, the entry loop walks off the end of the heap-allocated property block. This is a classic CWE-125 (Out-of-bounds Read): the root cause is a missing upper-bound/length-validation check on attacker-influenced length metadata prior to a loop that dereferences based on that length. The CPE data scopes this strictly to cpe:2.3:o:linux:linux_kernel across many versions, including 7.1 rc1/rc2/rc3, confirming this is a mainline/stable kernel defect rather than a distribution-specific or userland issue.

RemediationAI

Vendor-released patch: upgrade to the fixed stable release for your branch - 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13, or 7.1 (or later) - which adds the bounds check rejecting directories whose content extends past the block; commits are published at https://git.kernel.org/stable/c/ (e.g., 0a32040a48db8cf35de48b85d6115df5623e4964 and the sibling stable hashes) and tracked at https://nvd.nist.gov/vuln/detail/CVE-2026-53149. If immediate patching is not possible, reduce exposure with targeted compensating controls: disable the Thunderbolt/USB4 subsystem where it is not needed (blacklist the thunderbolt module or set CONFIG_USB4=n on rebuild), and enable Thunderbolt/USB4 device authorization / IOMMU-based DMA protection and BIOS 'Thunderbolt security level' so untrusted devices are not auto-connected - the trade-off is that legitimate Thunderbolt docks, displays, and peripherals will require explicit approval or stop working. As physical/peripheral hardening, apply a hotplug policy that ignores or requires manual authorization for newly attached Thunderbolt devices.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Image SLES15-SP7-Azure-3P Image SLES15-SP7-Azure-Basic Image SLES15-SP7-Azure-Standard Image SLES15-SP7-HPC-Azure Affected
Image SLES15-SP7-BYOS-Azure Image SLES15-SP7-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-Aliyun Image SLES15-SP7-CHOST-BYOS-Azure Image SLES15-SP7-CHOST-BYOS-EC2 Image SLES15-SP7-CHOST-BYOS-GCE Image SLES15-SP7-CHOST-BYOS-GDC Image SLES15-SP7-CHOST-BYOS-SAP-CCloud Image SLES15-SP7-EC2 Image SLES15-SP7-EC2-ECS-HVM Image SLES15-SP7-GCE Image SLES15-SP7-HPC-BYOS-Azure Image SLES15-SP7-HPC-BYOS-EC2 Image SLES15-SP7-HPC-BYOS-GCE Image SLES15-SP7-Hardened-BYOS-Azure Image SLES15-SP7-Hardened-BYOS-EC2 Image SLES15-SP7-Hardened-BYOS-GCE Image SLES15-SP7-SAPCAL-Azure Image SLES15-SP7-SAPCAL-EC2 Image SLES15-SP7-SAPCAL-GCE Affected
Image SLES15-SP7-SAP-Azure Image SLES15-SP7-SAP-Azure-3P Image SLES15-SP7-SAP-BYOS-Azure Image SLES15-SP7-SAP-BYOS-EC2 Image SLES15-SP7-SAP-BYOS-GCE Image SLES15-SP7-SAP-EC2 Image SLES15-SP7-SAP-GCE Image SLES15-SP7-SAP-Hardened-Azure Image SLES15-SP7-SAP-Hardened-BYOS-Azure Image SLES15-SP7-SAP-Hardened-BYOS-EC2 Image SLES15-SP7-SAP-Hardened-BYOS-GCE Image SLES15-SP7-SAP-Hardened-GCE Affected
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed

Share

CVE-2026-53149 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy