Kernel memory corruption via stale q_vector pointer
Published Sep 15, 2025 · Updated Sep 15, 2025
A use-after-free in the Linux kernel igb driver allows local users to corrupt kernel memory when q_vector allocation fails. In igb_alloc_q_vector(), failed allocation cleanup frees a preexisting q_vector but leaves its pointer in adapter->q_vector[v_idx]. Exploitation requires low-privileged local access, an applicable igb device, and memory pressure; subsequent pointer use can crash the kernel or alter kernel data.
Summary
What happened
A use-after-free in the Linux kernel igb driver allows local users to corrupt kernel memory when q_vector allocation fails. In igb_alloc_q_vector(), failed allocation cleanup frees a preexisting q_vector but leaves its pointer in adapter->q_vector[v_idx]. Exploitation requires low-privileged local access, an applicable igb device, and memory pressure; subsequent pointer use can crash the kernel or alter kernel data.
The record
- CVE
- CVE-2022-50252
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 15, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0200f0fbb11e359cc35af72ab10b2ec224e6f633
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0668716506ca66f90d395f36ccdaebc3e0e84801
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <314f7092b27749bdde44c14095b5533afa2a3bc8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3cb18dea11196fb4a06f78294cec5e61985e1aff
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <56483aecf6b22eb7dff6315b3a174688c6ad494c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <64ca1969599857143e91aeec4440640656100803
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <68e8adbcaf7a8743e473343b38b9dad66e2ac6f3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e399577bd397a517df4b938601108c63769ce0a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f96bd8adc8adde25390965a8c1ee81b73cb62075
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.
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