Bug 2270075 (CVE-2023-52612)
Summary: | CVE-2023-52612 kernel: crypto: scomp - fix req->dst buffer overflow | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Zack Miele <zmiele> |
Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | acaringi, allarkin, aquini, bhu, chwhite, cye, cyin, dbohanno, debarbos, dfreiber, drow, dvlasenk, esandeen, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, mleitner, mmilgram, mstowell, nmurray, ptalbert, rparrazo, rrobaina, rvrbovsk, rysulliv, scweaver, sidakwo, sukulkar, tglozar, tyberry, vkumar, wcosta, williams, wmealing, ycote, ykopkova, zhijwang |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | kernel 4.19.306, kernel 5.4.268, kernel 5.10.209, kernel 5.15.148, kernel 6.1.75, kernel 6.6.14, kernel 6.7.2, kernel 6.8 | Doc Type: | If docs needed, set a value |
Doc Text: |
A vulnerability was found in scomp component Linux Kernel causing a buffer overflow in the req->dst buffer. This occurred because the buffer size was not checked before copying data from scomp_scratch->dst, leading to potential overflow and DoS.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2270076 | ||
Bug Blocks: | 2270105 |
Description
Zack Miele
2024-03-18 13:02:55 UTC
Created kernel tracking bugs for this issue: Affects: fedora-all [bug 2270076] This was fixed for Fedora with the 6.6.14 stable kernel updates. The result of automatic check (that is developed by Alexander Larkin) for this CVE-2023-52612 is: CHECK Maybe valid. Check manually. with impact MODERATE (that is approximation based on flags OOB SIMPLEFIX ; these flags parsed automatically based on patche 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. |