CVE-2026-64124: net: devmem: reject dma-buf bind with non-page-aligned size or SG length

Published Jul 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

net: devmem: reject dma-buf bind with non-page-aligned size or SG length

netdevmembinddmabuf() trusts dmabuf->size and sgdmalen() to be PAGESIZE multiples without checking:

- txvec is sized dmabuf->size / PAGESIZE, and netdevmemgetniovat() only bounds-checks virtaddr < dmabuf->size before indexing txvec[virtaddr / PAGESIZE]. With size = NPAGESIZE + r (1 <= r < PAGESIZE), sendmsg() at iovbase = NPAGESIZE passes the bound check and reads txvec[N] -- one past.

- owner->area.numniovs = len / PAGESIZE while genpooladdowner() covers the full byte len, so a non-page-multiple non-final sg desyncs numniovs from the genpool region for every later sg, on both RX and TX.

dma-buf does not require page-aligned sizes, so the bind path has to enforce what its own indexing assumes. Reject both with -EINVAL.

The size check is TX-only (only txvec is sized off dmabuf->size); the SG-length check covers both directions.

Affected Software

7 affected components
Linux Linux kernel
Linux Linux kernel>=6.16<6.18.35
Linux Linux kernel>=6.19<7.0.11
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Modify the dma-buf bind path to enforce the assumptions used for tx_vec indexing: reject dma-buf bind when (1) dma-buf size is not a PAGE_SIZE multiple and (2) SG length is not a PAGE_SIZE multiple (including the (N*PAGE_SIZE + r) case), returning -EINVAL; ensure SG-length checks cover both directions (RX and TX), so indexing cannot read tx_vec one past the allocated region.

    Linux kernel net/devmem (net_devmem_bind_dmabuf / net_devmem_get_niov_at) Reject dma-buf bind with non-page-aligned dma-buf size or non-page-multiple/SG length = -EINVAL

Event History

Jul 19, 2026
CVE Published
via MITRE·03:40 PM
Data Sourced
via MITRE·03:40 PM
DescriptionSeverity
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-64124?

CVE-2026-64124 has a severity score of 8.8, classified as high.

2

What systems are affected by CVE-2026-64124?

CVE-2026-64124 affects the Linux kernel.

3

How do I fix CVE-2026-64124?

To fix CVE-2026-64124, update the Linux kernel to the latest patched version.

4

What is the risk associated with CVE-2026-64124?

CVE-2026-64124 has a risk level of 76, indicating significant potential impact.

5

What type of vulnerability is CVE-2026-64124?

CVE-2026-64124 is a vulnerability related to improper handling of dma-buf binds in the Linux kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203