Kernel memory corruption via unchecked SRQ max_sge
Published Jul 12, 2024 · Updated Aug 5, 2026
Improper input validation in the Linux kernel mlx5 RDMA driver allows local users to corrupt kernel memory through an oversized SRQ max_sge value. In mlx5_ib_create_srq(), the driver copies max_sge into the SRQ geometry and sizes descriptors from it without first enforcing the device maximum. Reachability requires local access to an mlx5 RDMA device and permission to create an SRQ; the resulting geometry mismatch can crash the host or corrupt kernel memory.
Summary
What happened
Improper input validation in the Linux kernel mlx5 RDMA driver allows local users to corrupt kernel memory through an oversized SRQ max_sge value. In mlx5_ib_create_srq(), the driver copies max_sge into the SRQ geometry and sizes descriptors from it without first enforcing the device maximum. Reachability requires local access to an mlx5 RDMA device and permission to create an SRQ; the resulting geometry mismatch can crash the host or corrupt kernel memory.
The record
- CVE
- CVE-2024-40990
- Published
- Jul 12, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.11
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <1e692244bf7dd827dd72edc6c4a3b36ae572f03c
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <36ab7ada64caf08f10ee5a114d39964d1f91e81d
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <4ab99e3613139f026d2d8ba954819e2876120ab3
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <7186b81c1f15e39069b1af172c6a951728ed3511
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <999586418600b4b3b93c2a0edd3a4ca71ee759bf
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <e0deb0e9c967b61420235f7f17a4450b4b4d6ce2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo