Resource Leak The advisory has been revoked - it doesn't affect any version of package kernel-modules-partner  (opens in a new tab)


Threat Intelligence

EPSS
0.22% (13th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-KERNELMODULESPARTNER-7792570
  • published22 Aug 2024
  • disclosed21 Aug 2024

Introduced: 21 Aug 2024

CVE-2024-43873  (opens in a new tab)
CWE-402  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:9.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-modules-partner package and not the kernel-modules-partner package as distributed by RHEL.

In the Linux kernel, the following vulnerability has been resolved:

vhost/vsock: always initialize seqpacket_allow

There are two issues around seqpacket_allow:

  1. seqpacket_allow is not initialized when socket is created. Thus if features are never set, it will be read uninitialized.
  2. if VIRTIO_VSOCK_F_SEQPACKET is set and then cleared, then seqpacket_allow will not be cleared appropriately (existing apps I know about don't usually do this but it's legal and there's no way to be sure no one relies on this).

To fix: - initialize seqpacket_allow after allocation - set it unconditionally in set_features