Resource Injection Affecting kernel-zfcpdump-core package, versions *


Severity

Recommended
low

Based on CentOS security rating.

Threat Intelligence

EPSS
0.04% (11th 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-CENTOS9-KERNELZFCPDUMPCORE-7471593
  • published17 Jul 2024
  • disclosed16 Jul 2024

Introduced: 16 Jul 2024

CVE-2022-48819  (opens in a new tab)
CWE-99  (opens in a new tab)

How to fix?

There is no fixed version for Centos:9 kernel-zfcpdump-core.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-zfcpdump-core package and not the kernel-zfcpdump-core package as distributed by Centos. See How to fix? for Centos:9 relevant fixed versions and status.

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

tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case

syzbot found that mixing sendpage() and sendmsg(MSG_ZEROCOPY) calls over the same TCP socket would again trigger the infamous warning in inet_sock_destruct()

WARN_ON(sk_forward_alloc_get(sk));

While Talal took into account a mix of regular copied data and MSG_ZEROCOPY one in the same skb, the sendpage() path has been forgotten.

We want the charging to happen for sendpage(), because pages could be coming from a pipe. What is missing is the downgrading of pure zerocopy status to make sure sk_forward_alloc will stay synced.

Add tcp_downgrade_zcopy_pure() helper so that we can use it from the two callers.

CVSS Scores

version 3.1