68dec754fd
An out-of-bounds read vulnerability was found in DPDK's Vhost library checksum offload feature. This issue enables an untrusted or compromised guest to crash the hypervisor's vSwitch by forging Virtio descriptors to cause out-of-bounds reads. This flaw allows an attacker with a malicious VM using a virtio driver to cause the vhost-user side to crash by sending a packet with a Tx checksum offload request and an invalid csum_start offset. References: https://nvd.nist.gov/vuln/detail/CVE-2024-11614 https://security-tracker.debian.org/tracker/CVE-2024-11614 Upstream-patch: https://git.dpdk.org/dpdk/commit/?id=4dc4e33ffa108e945fc8a1e2bbc7819791faa61e Signed-off-by: Divya Chellam <divya.chellam@windriver.com> Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> |
||
|---|---|---|
| conf | ||
| dynamic-layers/clang-layer/recipes-support/xdp-tools | ||
| recipes-extended/dpdk | ||
| COPYING.MIT | ||
| LICENSE | ||
| README | ||
meta-dpdk
This README file contains information on building the DPDK package.
Dependencies
This layer depends on:
URI: git://git.openembedded.org/bitbake branch: master
URI: git://git.openembedded.org/openembedded-core layers: meta branch: master
Guidelines for submitting patches
Please submit any patches against meta-dpdk to the meta-intel mailing list (meta-intel@lists.yoctoproject.org). Also, if your patches are available via a public git repository, please also include a URL to the repo and branch containing your patches as that makes it easier for maintainers to grab and test your patches.
There are patch submission scripts available that will, among other things, automatically include the repo URL and branch as mentioned. Please see the Yocto Project Development Manual sections entitled 'Using Scripts to Push a Change Upstream and Request a Pull' and 'Using Email to Submit a Patch' for details.
Regardless of how you submit a patch or patchset, the patches should at minimum follow the suggestions outlined in the 'Submitting a Change to the Yocto Project' section in the Yocto Project Development Manual. Specifically, they should:
-
Include a 'Signed-off-by:' line. A commit can't legally be pulled in without this.
-
Provide a single-line, short summary of the change. This short description should be prefixed by the BSP or recipe name, as appropriate, followed by a colon. Capitalize the first character of the summary (following the colon).
-
For the body of the commit message, provide detailed information that describes what you changed, why you made the change, and the approach you used.
-
If the change addresses a specific bug or issue that is associated with a bug-tracking ID, include a reference to that ID in your detailed description in the following format: [YOCTO #].
-
Pay attention to line length - please don't allow any particular line in the commit message to stretch past 72 characters.
-
For any non-trivial patch, provide information about how you tested the patch, and for any non-trivial or non-obvious testing setup, provide details of that setup.
Doing a quick 'git log' in meta-dpdk will provide you with many examples of good example commits if you have questions about any aspect of the preferred format.
The meta-dpdk maintainers will do their best to review and/or pull in a patch or patchset within 24 hours of the time it was posted. For larger and/or more involved patches and patchsets, the review process may take longer.
Maintainer: Anuj Mittal anuj.mittal@intel.com