In the Linux kernel, the following vulnerability has been resolved: staging: vme_user: bound slave read/write to the kern_buf size The SLAVE-path… (CVE-2026-64449)
A vulnerability in the Linux kernel's vme_user staging driver allowed out-of-bounds read/write operations due to improper bounding of buffer offsets and counts. The issue involved the SLAVE-path helpers buffer_to_user() and buffer_from_user() copying data beyond the fixed-size kernel buffer when the user-supplied window size exceeded the buffer size. This could lead to memory corruption. The flaw was identified by static analysis and confirmed with dynamic testing under KASAN. The vulnerability has been resolved by clamping the count against the kernel buffer size and returning early if the offset is beyond the buffer end.
AI Analysis
Technical Summary
The Linux kernel's vme_user driver had a vulnerability where the SLAVE-path helpers buffer_to_user() and buffer_from_user() copied 'count' bytes into or out of a fixed-size kernel buffer (128 KiB) without properly bounding the sum of the offset (*ppos) and count against the buffer size. The user-supplied slave window size could exceed this buffer size, allowing read/write operations to overflow the kernel buffer. This was fixed by adding clamping logic to ensure that the count does not exceed the kernel buffer size and that operations do not proceed if the offset is beyond the buffer end. The issue was found through static analysis tools (CodeQL and CBMC) and confirmed with Kernel Address Sanitizer (KASAN) testing, which detected slab-out-of-bounds writes during vme_user_write().
Potential Impact
This vulnerability could cause out-of-bounds memory accesses in kernel space, potentially leading to memory corruption, system instability, or crashes. No known exploits in the wild have been reported. The impact is limited to systems using the vulnerable vme_user staging driver with user-configured slave window sizes exceeding the kernel buffer size.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to clamp the read/write count against the fixed kernel buffer size and prevent out-of-bounds accesses. Users should update to a Linux kernel version that includes this fix. Since this is not a cloud service, remediation depends on applying the official kernel patch. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories or source repositories for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: staging: vme_user: bound slave read/write to the kern_buf size The SLAVE-path… (CVE-2026-64449)
Description
A vulnerability in the Linux kernel's vme_user staging driver allowed out-of-bounds read/write operations due to improper bounding of buffer offsets and counts. The issue involved the SLAVE-path helpers buffer_to_user() and buffer_from_user() copying data beyond the fixed-size kernel buffer when the user-supplied window size exceeded the buffer size. This could lead to memory corruption. The flaw was identified by static analysis and confirmed with dynamic testing under KASAN. The vulnerability has been resolved by clamping the count against the kernel buffer size and returning early if the offset is beyond the buffer end.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's vme_user driver had a vulnerability where the SLAVE-path helpers buffer_to_user() and buffer_from_user() copied 'count' bytes into or out of a fixed-size kernel buffer (128 KiB) without properly bounding the sum of the offset (*ppos) and count against the buffer size. The user-supplied slave window size could exceed this buffer size, allowing read/write operations to overflow the kernel buffer. This was fixed by adding clamping logic to ensure that the count does not exceed the kernel buffer size and that operations do not proceed if the offset is beyond the buffer end. The issue was found through static analysis tools (CodeQL and CBMC) and confirmed with Kernel Address Sanitizer (KASAN) testing, which detected slab-out-of-bounds writes during vme_user_write().
Potential Impact
This vulnerability could cause out-of-bounds memory accesses in kernel space, potentially leading to memory corruption, system instability, or crashes. No known exploits in the wild have been reported. The impact is limited to systems using the vulnerable vme_user staging driver with user-configured slave window sizes exceeding the kernel buffer size.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to clamp the read/write count against the fixed kernel buffer size and prevent out-of-bounds accesses. Users should update to a Linux kernel version that includes this fix. Since this is not a cloud service, remediation depends on applying the official kernel patch. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories or source repositories for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fqjm-fj8x-6hp3
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64449"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542089c2644c7f8082ce6
Added to database: 07/25/2026, 23:08:56 UTC
Last enriched: 07/25/2026, 23:20:09 UTC
Last updated: 07/26/2026, 05:07:56 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.