CVE-2022-50252 | In the Linux kernel, the following vulnerability has been resolved: igb: Do not free q_vector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc() fails, q_vector will be freed but left in the original adapter->q_vector[v_idx] array position.
In the Linux kernel, the following vulnerability has been resolved:
igb: Do not free q_vector unless new one was allocated
Avoid potential use-after-free condition under memory pressure. If the
kzalloc() fails, q_vector will be freed but left in the original
adapter->q_vector[v_idx] array position.
- 🔗 git.kernel.org/stable/c/64ca1969599857143e91aeec44406406…
- 🔗 git.kernel.org/stable/c/0200f0fbb11e359cc35af72ab10b2ec2…
- 🔗 git.kernel.org/stable/c/68e8adbcaf7a8743e473343b38b9dad6…
- 🔗 git.kernel.org/stable/c/f96bd8adc8adde25390965a8c1ee81b7…
- 🔗 git.kernel.org/stable/c/3cb18dea11196fb4a06f78294cec5e61…
- 🔗 git.kernel.org/stable/c/314f7092b27749bdde44c14095b5533a…
- 🔗 git.kernel.org/stable/c/6e399577bd397a517df4b938601108c6…
- 🔗 git.kernel.org/stable/c/56483aecf6b22eb7dff6315b3a174688…
```Code``` unterstützt. Zero-Day & Vulnerability Intelligence Hub
Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
| Tier | CVEs | Anteil |
|---|---|---|
| ≥90 % | 725 | 0,2 % |
| ≥50 % | 3.220 | 0,9 % |
| ≥10 % | 22.091 | 5,9 % |
| <10 % | 347.648 | 93,0 % |
CVE-2022-50252 | In the Linux kernel, the following vulnerability has been resolved: igb: Do not free q_vector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc() fails, q_vector will be freed but left in the original adapter->q_vector[v_idx] array position.
In the Linux kernel, the following vulnerability has been resolved: igb: Do not free q_vector unless new one was allocated Avoid potential use-after-free condition under memory pressure. If the kzalloc() fails, q_vector will be freed but
Noch keine Analyse zu CVE-2022-50252
Sei der Erste: Einschätzung, Betroffenheit, Workaround oder PoC — mit Antworten im Thread.