Bug 1228011 (CVE-2022-48864) - VUL-0: CVE-2022-48864: kernel: vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command
Summary: VUL-0: CVE-2022-48864: kernel: vdpa/mlx5: add validation for VIRTIO_NET_CTRL_...
Status: NEW
Alias: CVE-2022-48864
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/414282/
Whiteboard: CVSSv3.1:SUSE:CVE-2022-48864:5.5:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-17 08:11 UTC by SMASH SMASH
Modified: 2024-07-17 09:52 UTC (History)
2 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-07-17 08:11:41 UTC 
In the Linux kernel, the following vulnerability has been resolved:

vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command

When control vq receives a VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command
request from the driver, presently there is no validation against the
number of queue pairs to configure, or even if multiqueue had been
negotiated or not is unverified. This may lead to kernel panic due to
uninitialized resource for the queues were there any bogus request
sent down by untrusted driver. Tie up the loose ends there.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-48864
https://www.cve.org/CVERecord?id=CVE-2022-48864
https://git.kernel.org/stable/c/9f6effca75626c7a7c7620dabcb1a254ca530230
https://git.kernel.org/stable/c/e7e118416465f2ba8b55007e5b789823e101421e
https://git.kernel.org/stable/c/ed0f849fc3a63ed2ddf5e72cdb1de3bdbbb0f8eb
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2022/CVE-2022-48864.mbox
https://bugzilla.redhat.com/show_bug.cgi?id=2298208