Linux Kernel up to 7.0.12 thunderbolt value.text tb_property_entry_valid null termination

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k1.25-

Summaryinfo

A vulnerability was found in Linux Kernel up to 7.0.12. It has been rated as critical. Affected by this issue is the function tb_property_entry_valid of the file value.text of the component thunderbolt. Performing a manipulation results in null termination. This vulnerability is reported as CVE-2026-53150. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, was found in Linux Kernel up to 7.0.12. This affects the function tb_property_entry_valid of the file value.text of the component thunderbolt. The manipulation with an unknown input leads to a null termination vulnerability. CWE is classifying the issue as CWE-170. The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Reject zero-length property entries in validator tb_property_entry_valid() accepts entries with length == 0 for DIRECTORY, DATA, and TEXT types. A zero-length TEXT entry passes validation but causes an underflow in the null-termination logic: property->value.text[property->length * 4 - 1] = '\0'; When property->length is 0 this writes to offset -1 relative to the allocation. Reject zero-length entries early in the validator since they have no valid representation in the XDomain property protocol.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-53150 since 06/09/2026. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/25/2026).

Upgrading to version 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36 or 7.0.13 eliminates this vulnerability. Applying the patch 581c2053ab4dbe27e83c9e62deb4c73aa8dc0c3a/35d6c9252a152e756768a26dbf216b9dd9dd8e92/99d9dbad1463afb510d42c9714f846361d1b726d/5f56bc6bddffe8710ba0ba8844023b5a44ca90e4/ca11e7da4fba4b394f69e16448f4463c44c84de6/2e0ddac549ebd713eb9f4a15b6496e3440a17d8b/3b6e68cb97f725385010264a873e14a3921b6b8a/cff8eb65d1eafe7793e54b4d0cf6bf831644630b is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Null termination
CWE: CWE-170 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.259/5.15.210/6.1.176/6.6.143/6.12.94/6.18.36/7.0.13
Patch: 581c2053ab4dbe27e83c9e62deb4c73aa8dc0c3a/35d6c9252a152e756768a26dbf216b9dd9dd8e92/99d9dbad1463afb510d42c9714f846361d1b726d/5f56bc6bddffe8710ba0ba8844023b5a44ca90e4/ca11e7da4fba4b394f69e16448f4463c44c84de6/2e0ddac549ebd713eb9f4a15b6496e3440a17d8b/3b6e68cb97f725385010264a873e14a3921b6b8a/cff8eb65d1eafe7793e54b4d0cf6bf831644630b

Timelineinfo

06/09/2026 CVE reserved
06/25/2026 +16 days Advisory disclosed
06/25/2026 +0 days VulDB entry created
06/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-53150 (🔒)
GCVE (CVE): GCVE-0-2026-53150
GCVE (VulDB): GCVE-100-373737

Entryinfo

Created: 06/25/2026 12:12
Changes: 06/25/2026 12:12 (60)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!