Bug 2278932 (CVE-2022-48689) - CVE-2022-48689 kernel: tcp: TX zerocopy should not sense pfmemalloc status
Summary: CVE-2022-48689 kernel: tcp: TX zerocopy should not sense pfmemalloc status
Keywords:
Status: NEW
Alias: CVE-2022-48689
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2279002
TreeView+ depends on / blocked
 
Reported: 2024-05-03 18:41 UTC by Marco Benatto
Modified: 2024-06-09 16:44 UTC (History)
49 users (show)

Fixed In Version: kernel 5.15.68, kernel 5.19.9, kernel 6.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Marco Benatto 2024-05-03 18:41:28 UTC
In the Linux kernel, the following vulnerability has been resolved:

tcp: TX zerocopy should not sense pfmemalloc status

The Linux kernel CVE team has assigned CVE-2022-48689 to this issue.

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2024050345-CVE-2022-48689-5ee7@gregkh/T

Comment 2 Alex 2024-06-09 16:44:33 UTC
The result of automatic check (that is developed by Alexander Larkin) for this CVE-2022-48689 is: CHECK	Maybe valid. Check manually. with impact LOW (that is an approximation based on flags WRITE KASAN DISK INIT RACE SKB  ; these flags parsed automatically based on patch data). Such automatic check happens only for Low/Moderates (and only when not from reporter, but parsing already existing CVE). Highs always checked manually (I check it myself and then we check it again in Remediation team). In rare cases some of the Moderates could be increased to High later.


Note You need to log in before you can comment on or make changes to this bug.