CVE-2026-63893
Last modified
CVE-2026-63893 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: thunderbolt: property: Reject u32 wrap in tb_property_entry_valid() entry->value is u32 and entry->length is u16; the sum is performed in u32 and wraps. A malicious XDomain peer can pick value = 0xffffff00, length = 0x100 so the sum 0x100000000 wraps to 0 and passes the > block_len check. EPSS estimates a 0.39% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: property: Reject u32 wrap in tb_property_entry_valid() entry->value is u32 and entry->length is u16; the sum is performed in u32 and wraps. A malicious XDomain peer can pick value = 0xffffff00, length = 0x100 so the sum 0x100000000 wraps to 0 and passes the > block_len check. tb_property_parse() then passes entry->value to parse_dwdata() as a dword offset into the property block, reading attacker-directed memory far past the allocation. For TEXT-typed entries with the "deviceid" or "vendorid" keys this lands in xd->device_name / xd->vendor_name and is readable back via the per-XDomain device_name / vendor_name sysfs attributes; the leak is NUL-bounded (kstrdup() stops at the first zero byte) and untargeted (the attacker picks a delta, not an absolute address). DATA-typed entries are parsed into property->value.data but not generically surfaced to userspace. Use check_add_overflow() so a wrapped sum is rejected.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.15, < 5.10.259 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.93 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.35 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.12 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-63893?
How severe is CVE-2026-63893?
How do I fix CVE-2026-63893?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-63888In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-63889In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-6389IBM Turbonomic prometurbo agent 8.16.0 through 8.17.6 IBM Tu…7.8
- CVE-2026-63890In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63891In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63892In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63894In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63895In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63896In the Linux kernel, the following vulnerability has been re…
- CVE-2026-63897In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-63898In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-63899In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-63893?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
