CVE-2022-48819

Source
https://cve.org/CVERecord?id=CVE-2022-48819
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48819.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-48819
Downstream
Published
2024-07-16T11:44:06.619Z
Modified
2026-04-02T08:27:02.149568Z
Summary
tcp: take care of mixed splice()/sendmsg(MSG_ZEROCOPY) case
Details

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(MSGZEROCOPY) calls over the same TCP socket would again trigger the infamous warning in inetsock_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 skforwardalloc will stay synced.

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

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48819.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
9b65b17db72313b7a4fe9bc9502928c88be57986
Fixed
47f3860c4931175f112f28dcac66eacca9b1040f
Fixed
f8d9d938514f46c4892aff6bfe32f425e84d81cc

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48819.json"