Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-63892thunderbolt: property: Reject dir_len < 4 to prevent size_t underflow

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 months later

    First scored

    High 7.1

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-63892, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected cdae7c07e3e3509eaabc18c1640a55dc5b99c179 – < 37abc4504fa19d8f9f1e87792e8a2b8fdb308e40
    • affected cdae7c07e3e3509eaabc18c1640a55dc5b99c179 – < e2d4d51cf5785815fa4e91e0c019e3eb2506a84c
    • affected cdae7c07e3e3509eaabc18c1640a55dc5b99c179 – < de618299190b418291609e6921557253bd417e25
    • affected cdae7c07e3e3509eaabc18c1640a55dc5b99c179 – < 5506c825f14d810f0690b1f4367cb7249ebb387a
    • affected cdae7c07e3e3509eaabc18c1640a55dc5b99c179 – < 542a13890b742099c461d70920e97b14e568f6ec
    • affected cdae7c07e3e3509eaabc18c1640a55dc5b99c179 – < d548179adcc87e1bc66b17e00352a1f536e76065
    • affected cdae7c07e3e3509eaabc18c1640a55dc5b99c179 – < 3bec49ca55e08fb085cc4318f24b1b37eaab28cb
    • affected cdae7c07e3e3509eaabc18c1640a55dc5b99c179 – < de21b59c29e31c5108ddc04210631bbfab81b997
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-63892 badge
[![CVE-2026-63892](https://cveledger.app/badge/CVE-2026-63892.svg)](https://cveledger.app/cve/CVE-2026-63892)

Record last updated .