CVE-2026-63892: thunderbolt: property: Reject dir_len < 4 to prevent size_t underflow
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 37abc4504fa19d8f9f1e87792e8a2b8fdb308e40, 3bec49ca55e08fb085cc4318f24b1b37eaab28cb, 542a13890b742099c461d70920e97b14e568f6ec.
Low priority for now. Upgrade to Linux Linux 37abc4504fa19d8f9f1e87792e8a2b8fdb308e40, 3bec49ca55e08fb085cc4318f24b1b37eaab28cb, 542a13890b742099c461d70920e97b14e568f6ec or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: property: Reject dir_len < 4 to prevent size_t underflow On the non-root path, __tb_property_parse_dir() takes dir_len from entry->length (u16 widened to size_t). Two distinct OOB conditions follow when entry->length < 4: 1. The non-root path begins with kmemdup(&block[dir_offset], sizeof(*dir->uuid), ...) which always reads 4 dwords from dir_offset. tb_property_entry_valid() only enforces dir_offset + entry->length <= block_len, so a crafted entry with dir_offset close to the end of the property block and entry->length in 0..3 passes that gate but lets the UUID copy run off the block (e.g. dir_offset = 497, dir_len = 3 in a 500-dword block reads block[497..501]). 2. After the kmemdup, content_len = dir_len - 4 underflows size_t to ~SIZE_MAX, nentries becomes SIZE_MAX / 4, and the entry walk runs OOB on each iteration until an entry fails validation or the kernel oopses on an unmapped page. Reject dir_len < 4 on the non-root path *before* the UUID kmemdup, which closes both holes. Also move INIT_LIST_HEAD(&dir->properties) up to immediately after the dir allocation so the new error-return path (and the existing uuid-alloc failure path) calling tb_property_free_dir() sees a walkable list rather than the zero-initialized NULL next/prev that list_for_each_entry_safe() would oops on.
- Published
- Jul 19, 2026
- Updated
- Jul 27, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.15affected
- cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and later · before 37abc4504fa19d8f9f1e87792e8a2b8fdb308e40affected · git
- cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and later · before e2d4d51cf5785815fa4e91e0c019e3eb2506a84caffected · git
- cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and later · before de618299190b418291609e6921557253bd417e25affected · git
- cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and later · before 5506c825f14d810f0690b1f4367cb7249ebb387aaffected · git
- cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and later · before 542a13890b742099c461d70920e97b14e568f6ecaffected · git
- cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and later · before d548179adcc87e1bc66b17e00352a1f536e76065affected · git
- cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and later · before 3bec49ca55e08fb085cc4318f24b1b37eaab28cbaffected · git
- cdae7c07e3e3509eaabc18c1640a55dc5b99c179 and later · before de21b59c29e31c5108ddc04210631bbfab81b997affected · git
- before 4.15not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.12-1 | 7.0.12-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-63834Jul 19, 2026 · batman-adv: tp_meter: restrict number of unacked list entries0Monitor
- ← EarlierCVE-2026-63810Jul 19, 2026 · block: Avoid mounting the bdev pseudo-filesystem in userspace0Monitor
- Later →CVE-2026-63894Jul 19, 2026 · usb: gadget: f_fs: serialize DMABUF cancel against request completion31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 37abc4504fa19d8f9f1e87792e8a2b8fdb308e40 | Vendor (CNA) |
| Linux Linux | 3bec49ca55e08fb085cc4318f24b1b37eaab28cb | Vendor (CNA) |
| Linux Linux | 542a13890b742099c461d70920e97b14e568f6ec | Vendor (CNA) |
| Linux Linux | 5506c825f14d810f0690b1f4367cb7249ebb387a | Vendor (CNA) |
| Linux Linux | d548179adcc87e1bc66b17e00352a1f536e76065 | Vendor (CNA) |
| Linux Linux | de21b59c29e31c5108ddc04210631bbfab81b997 | Vendor (CNA) |
| Linux Linux | de618299190b418291609e6921557253bd417e25 | Vendor (CNA) |
| Linux Linux | e2d4d51cf5785815fa4e91e0c019e3eb2506a84c | Vendor (CNA) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3bec49ca55e08fb085cc4318f24b1b37eaab28cb
- git.kernel.org/stable/c/542a13890b742099c461d70920e97b14e568f6ec
- git.kernel.org/stable/c/5506c825f14d810f0690b1f4367cb7249ebb387a
- git.kernel.org/stable/c/d548179adcc87e1bc66b17e00352a1f536e76065
- git.kernel.org/stable/c/de21b59c29e31c5108ddc04210631bbfab81b997
- git.kernel.org/stable/c/de618299190b418291609e6921557253bd417e25
- git.kernel.org/stable/c/e2d4d51cf5785815fa4e91e0c019e3eb2506a84c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.