Linux Kernel up to 7.0.6 dm Remaining buffer overflow

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.
7.6$5k-$25k0.63

Summaryinfo

A vulnerability classified as critical has been found in Linux Kernel up to 7.0.6. Affected by this issue is some unknown functionality of the component dm. Performing a manipulation of the argument Remaining results in buffer overflow. This vulnerability is cataloged as CVE-2026-46294. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.0.6. It has been classified as critical. This affects some unknown processing of the component dm. The manipulation of the argument remaining with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: dm: fix a buffer overflow in ioctl processing Tony Asleson (using Claude) found a buffer overflow in dm-ioctl in the function retrieve_status: 1. The code in retrieve_status checks that the output string fits into the output buffer and writes the output string there 2. Then, the code aligns the "outptr" variable to the next 8-byte boundary: outptr = align_ptr(outptr); 3. The alignment doesn't check overflow, so outptr could point past the buffer end 4. The "for" loop is iterated again, it executes: remaining = len - (outptr - outbuf); 5. If "outptr" points past "outbuf + len", the arithmetics wraps around and the variable "remaining" contains unusually high number 6. With "remaining" being high, the code writes more data past the end of the buffer Luckily, this bug has no security implications because: 1. Only root can issue device mapper ioctls 2. The commonly used libraries that communicate with device mapper (libdevmapper and devicemapper-rs) use buffer size that is aligned to 8 bytes - thus, "outptr = align_ptr(outptr)" can't overshoot the input buffer and the bug can't happen accidentally

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

Upgrading to version 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7 or 7.1-rc1 eliminates this vulnerability. Applying the patch c8c5311237448f6ffeecc9aec2362e3692623668/448ee8fb79c26a26599ffa4b2adeb4322d3d3d8c/526ff9126a0ae087b65726e1faf31114c718020d/f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a/d271631023cbe1cbe7c31a0275ab797883be6e0a/5af6a879e915ae7bcd83695c316ebb32e1c61bc2/8daa6c708ef524089ae43f2aed9190acb26d7df8/2fa49cc884f6496a915c35621ba4da35649bf159 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: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Buffer overflow
CWE: CWE-120 / 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.258/5.15.209/6.1.175/6.6.140/6.12.88/6.18.30/7.0.7/7.1-rc1
Patch: c8c5311237448f6ffeecc9aec2362e3692623668/448ee8fb79c26a26599ffa4b2adeb4322d3d3d8c/526ff9126a0ae087b65726e1faf31114c718020d/f0b0b09d9840838ae77ccdd6a62de0daef4e6e0a/d271631023cbe1cbe7c31a0275ab797883be6e0a/5af6a879e915ae7bcd83695c316ebb32e1c61bc2/8daa6c708ef524089ae43f2aed9190acb26d7df8/2fa49cc884f6496a915c35621ba4da35649bf159

Timelineinfo

05/13/2026 CVE reserved
06/08/2026 +26 days Advisory disclosed
06/08/2026 +0 days VulDB entry created
06/08/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-46294 (🔒)
GCVE (CVE): GCVE-0-2026-46294
GCVE (VulDB): GCVE-100-369249

Entryinfo

Created: 06/08/2026 20:12
Changes: 06/08/2026 20:12 (59)
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!